CN116828546A

CN116828546A - Session channel establishment method, device and equipment of non-3 GPP equipment

Info

Publication number: CN116828546A
Application number: CN202210323948.5A
Authority: CN
Inventors: 李欢; 谢振华
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2022-03-22
Filing date: 2022-03-29
Publication date: 2023-09-29

Abstract

The application discloses a method, a device and equipment for establishing a session channel of non-3 GPP equipment, belonging to the technical field of communication, wherein the method provided by the embodiment of the application comprises the following steps: the terminal equipment acquires a session policy of the non-3 GPP equipment; the terminal equipment requests the core network equipment to establish a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

Description

Session channel establishment method, device and equipment of non-3 GPP equipment

Technical Field

The application belongs to the technical field of communication, and particularly relates to a method, a device and equipment for establishing a session channel of non-3 GPP equipment.

Background

The current 3GPP 5G core network supports fixed network access, including supporting a home gateway (Residential Gateway, RG) to access the 5G core network through the fixed network and the 3GPP network, and also including a 3GPP terminal device (UE) to access the 5G core network through the home gateway.

Only schemes are defined in the current art for 3GPP devices to access a 5G system (5 GS) through a 5G home gateway (5G-RG). There may be scenarios where non-3 GPP devices access 5GS through 5G-RG. For example, in a home, a tablet, watch, television, etc. is accessed through a home gateway, hopefully with 5GS for service. Different non-3 GPP devices may have different service requirements, and the same non-3 GPP device may also have different service requirements, so that the current technology cannot provide appropriate QoS support for the different service requirements of the non-3 GPP device, and thus the service requirements of the non-3 GPP device cannot be met.

Disclosure of Invention

The embodiment of the application provides a method, a device and equipment for establishing a session channel of non-3 GPP equipment, which can solve the problem that a 5G system in the prior art cannot meet the service requirement of the non-3 GPP equipment.

In a first aspect, a method for establishing a session channel of a non-3 GPP device is provided, including:

the terminal equipment acquires a session policy of the non-3 GPP equipment;

the terminal equipment requests the core network equipment to establish a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

In a second aspect, a method for establishing a session channel of a non-3 GPP device is provided, including:

the core network equipment acquires a session policy of the non-3 GPP equipment;

the core network device establishes a session channel for the non-3 GPP device according to the session policy of the non-3 GPP device and the request of the terminal device; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

In a third aspect, a session channel establishment apparatus of a non-3 GPP device is provided, including:

the first acquisition module is used for acquiring the session policy of the non-3 GPP equipment;

A request establishing module, configured to request a core network device to establish a session channel for the non-3 GPP device according to a session policy of the non-3 GPP device; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

In a fourth aspect, a session channel establishment apparatus of a non-3 GPP device is provided, including:

a second acquisition module, configured to acquire a session policy of a non-3 GPP device;

the establishing module is used for establishing a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment and the request of the terminal equipment; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

In a fifth aspect, there is provided a terminal device comprising a processor and a memory storing a program or instructions executable on the processor, which program or instructions when executed by the processor implement the steps of the method as described in the first aspect.

A sixth aspect provides a terminal device, including a processor and a communication interface, where the communication interface is configured to obtain a session policy of a non-3 GPP device; the processor is used for requesting the core network equipment to establish a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

In a seventh aspect, a network side device is provided, comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the method as described in the second aspect.

An eighth aspect provides a network side device, including a processor and a communication interface, where the communication interface is configured to obtain a session policy of a non-3 GPP device; the processor is used for establishing a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment and the request of the terminal equipment; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

In a ninth aspect, there is provided a communication system comprising: a terminal device operable to perform the steps of the method as described in the first aspect, and a network side device operable to perform the steps of the method as described in the second aspect.

In a tenth aspect, there is provided a readable storage medium having stored thereon a program or instructions which when executed by a processor, performs the steps of the method according to the first aspect or performs the steps of the method according to the second aspect.

In an eleventh aspect, there is provided a chip comprising a processor and a communication interface coupled to the processor, the processor being for running a program or instructions to implement the method according to the first aspect or to implement the method according to the second aspect.

In a twelfth aspect, there is provided a computer program/program product stored in a storage medium, the computer program/program product being executed by at least one processor to implement the steps of the method as described in the first aspect, or to implement the steps of the method as described in the second aspect.

In the embodiment of the application, aiming at non-3 GPP equipment accessed to a 5G system through terminal equipment, the terminal equipment requests core network equipment to establish PDU session and/or QoS flow for the corresponding non-3 GPP equipment, so that the core network equipment carries out differentiated QoS management on the non-3 GPP equipment accessed from the terminal equipment; because different non-3 GPP devices may have different service requirements, the same non-3 GPP device may also have different service requirements, and the embodiment of the application can provide proper QoS support according to different service requirements, thereby not only meeting the service requirements of the device, but also reasonably using the resources of 5 GS.

Drawings

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

fig. 2 shows one of the step flowcharts of the session channel establishment method of the non-3 GPP device according to the embodiment of the present application;

fig. 3 is a second flowchart illustrating a session channel establishment method of a non-3 GPP device according to an embodiment of the present application;

FIG. 4 shows a flow chart of an example one provided by an embodiment of the present application;

FIG. 5 shows a flow chart of an example two provided by an embodiment of the present application;

FIG. 6 shows a flow chart of an example III provided by an embodiment of the present application;

fig. 7 is a schematic structural diagram of a session channel establishment apparatus of a non-3 GPP device according to an embodiment of the present application;

fig. 8 is a second schematic structural diagram of a session channel establishment apparatus of a non-3 GPP device according to an embodiment of the present application;

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

fig. 10 shows a schematic structural diagram of a terminal device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a network side device according to an embodiment of the present application.

Detailed Description

The technical solutions of the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which are derived by a person skilled in the art based on the embodiments of the application, fall within the scope of protection of the application.

The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the terms so used are interchangeable under appropriate circumstances such that the embodiments of the application are capable of operation in sequences other than those illustrated or otherwise described herein, and that the "first" and "second" distinguishing between objects generally are not limited in number to the extent that the first object may, for example, be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/" generally means a relationship in which the associated object is an "or" before and after.

It should be noted that the techniques described in the embodiments of the present application are not limited to long term evolution (Long Term Evolution, LTE)/LTE evolution (LTE-Advanced, LTE-a) systems, but may also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single carrier frequency division multiple access (Single-carrier Frequency Division Multiple Access, SC-FDMA), and other systems. The terms "system" and "network" in embodiments of the application are often used interchangeably, and the techniques described may be used for both the above-mentioned systems and radio technologies, as well as other systems and radio technologies. The following description describes a New air interface (NR) system for purposes of example and uses NR terminology in much of the description that follows, but these techniques are also applicable to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which an embodiment of the present application is applicable. The wireless communication system includes a terminal 11 and a network device 12. The terminal 11 may be a mobile phone, a tablet (Tablet Personal Computer), a Laptop (Laptop Computer) or a terminal-side Device called a notebook, a personal digital assistant (Personal Digital Assistant, PDA), a palm top, a netbook, an ultra-mobile personal Computer (ultra-mobile personal Computer, UMPC), a mobile internet appliance (Mobile Internet Device, MID), an augmented reality (augmented reality, AR)/Virtual Reality (VR) Device, a robot, a Wearable Device (weather Device), a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), a smart home (home Device with a wireless communication function, such as a refrigerator, a television, a washing machine, or a furniture), a game machine, a personal Computer (personal Computer, PC), a teller machine, or a self-service machine, and the Wearable Device includes: intelligent wrist-watch, intelligent bracelet, intelligent earphone, intelligent glasses, intelligent ornament (intelligent bracelet, intelligent ring, intelligent necklace, intelligent anklet, intelligent foot chain etc.), intelligent wrist strap, intelligent clothing etc.. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network-side device 12 may comprise an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (Radio Access Network, RAN), a radio access network function or a radio access network element. Access network device 12 may include a base station, a WLAN access point, a WiFi node, or the like, which may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a home node B, a home evolved node B, a transmission and reception point (Transmitting Receiving Point, TRP), or some other suitable terminology in the art, and the base station is not limited to a particular technical vocabulary so long as the same technical effect is achieved, and it should be noted that in the embodiment of the present application, only a base station in the NR system is described as an example, and the specific type of the base station is not limited. The core network device may include, but is not limited to, at least one of: core network nodes, core network functions, mobility management entities (Mobility Management Entity, MME), access mobility management functions (Access and Mobility Management Function, AMF), session management functions (Session Management Function, SMF), user plane functions (User Plane Function, UPF), policy control functions (Policy Control Function, PCF), policy and charging rules function units (Policy and Charging Rules Function, PCRF), edge application service discovery functions (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data repository (Unified Data Repository, UDR), home subscriber server (Home Subscriber Server, HSS), centralized network configuration (Centralized network configuration, CNC), network storage functions (Network Repository Function, NRF), network opening functions (Network Exposure Function, NEF), local NEF (or L-NEF), binding support functions (Binding Support Function, BSF), application functions (Application Function, AF), and the like. It should be noted that, in the embodiment of the present application, only the core network device in the NR system is described as an example, and the specific type of the core network device is not limited.

The method, the device and the equipment for establishing the session channel of the non-3 GPP equipment provided by the embodiment of the application are described in detail below through some embodiments and application scenes thereof with reference to the accompanying drawings.

As shown in fig. 2, an embodiment of the present application provides a method for establishing a session channel of a non-3 GPP device, including:

step 201, a terminal device acquires a session policy of a non-3 GPP device;

optionally, in this step, a session policy of the non-3 GPP device is used to describe how to establish a session channel for the non-3 GPP device.

Step 202, the terminal equipment requests a core network device to establish a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

In the embodiment of the application, aiming at non-3 GPP equipment accessed to a 5G system through terminal equipment, the terminal equipment requests core network equipment to establish PDU session and/or QoS flow for the corresponding non-3 GPP equipment, so that the core network equipment carries out differentiated QoS management on the non-3 GPP equipment accessed from the terminal equipment; thus, when the non-3 GPP device transmits data through the terminal device using the 5G network, the session management problem of the non-3 GPP device is solved, so that the non-3 GPP device is provided with proper service quality assurance.

It should be noted that, in the embodiment of the present application, the terminal device is a 3GPP terminal device, or a home gateway, which is not specifically limited herein.

As an optional embodiment, the session policy of the non-3 GPP device includes at least one of:

first indication information indicating one or more non-3 GPP devices to use one PDU session;

second indication information indicating that one or more non-3 GPP devices use one QoS flow.

As another optional embodiment, the session policy of the non-3 GPP device further comprises at least one of:

identification information of one or more non-3 GPP devices using one PDU session;

identification information of one or more non-3 GPP devices using one QoS flow;

establishment parameters of session channels.

Wherein the session channel establishment parameters include at least one of:

an IP type;

an Ethernet type;

a business continuity mode;

a control surface channel;

a user plane channel;

a data network name DNN of the session channel;

network slice identification of the session channel.

For example, the session channel establishment parameters may be used to indicate that different types of session channels are established. For example, a PDU session indicating establishment of a user plane channel (data transfer using a user plane, e.g., data transfer using an air interface user plane and an N3 user plane channel), a PDU session of a control plane channel (data transfer using control plane signaling, e.g., NAS message transfer using a terminal device), an optimized CP plane PDU session (data transfer using a control plane and a user plane, e.g., air interface user plane, control plane used between a radio network and a core network), an IP type PDU session, an ethernet type PDU session, a service continuity mode being a SSC (Session and Service Continuity, service continuity) mode 1 or a mode 2 or mode 3 PDU session.

In at least one embodiment of the present application, prior to step 202, the method further comprises:

the terminal equipment acquires the identification information of the non-3 GPP equipment; alternatively, the terminal device may acquire the identification information of the non-3 GPP device through a process in which the non-3 GPP device establishes a connection with the terminal device.

It should be noted that, the terminal device may acquire the identification information of the non-3 GPP device, which may be directly acquired by the terminal device on the connection between the non-3 GPP devices, or may be acquired by mapping after the terminal device acquires the first identification information of the non-3 GPP device on the connection between the non-3 GPP devices. The terminal device directly obtains the MAC address or the connection identifier of the non-3 GPP device on the connection between the non-3 GPP device and then maps the MAC address or the connection identifier of the non-3 GPP device to the type identifier of the non-3 GPP device.

It should be noted that, in the embodiment of the present application, the terminal device may be set with a mapping relationship between a device identifier or a connection identifier of a non-3 GPP device and a type identifier, or a user manually sets a type identifier of a specific non-3 GPP device, which is not specifically limited herein.

Accordingly, this step 202 includes:

And the terminal equipment requests the core network equipment to establish a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment and the identification information of the non-3 GPP equipment.

For example, the session policy indicates that one PDU session is established for a plurality of 3GPP devices, when the terminal device obtains the identification information of one non-3 GPP device, it may be first determined whether a PDU session corresponding to the identification information of the non-3 GPP device exists, and if so, the flow ends; if not, the core network is requested to establish a PDU session for the non-3 GPP device.

As an optional embodiment, the requesting, by the terminal device, the core network device to establish a session channel for the non-3 GPP device according to the session policy of the non-3 GPP device and the identification information of the non-3 GPP device includes:

the terminal equipment sends a first PDU (protocol data unit) session establishment request message or a first PDU session modification request message to core network equipment according to the session strategy of the non-3 GPP equipment and the identification information of the non-3 GPP equipment, wherein the first PDU session establishment request message is used for requesting to establish a PDU session for the non-3 GPP equipment, and the first PDU session modification request message is used for requesting to establish a QoS (quality of service) stream for the non-3 GPP equipment;

The terminal equipment receives a first PDU session establishment response message or a first PDU session modification response message sent by the core network equipment; the first PDU session establishment response message is used for indicating successful establishment of PDU session of the non-3 GPP equipment; the first PDU session modification response message is used for indicating successful establishment of QoS flow of the non-3 GPP equipment.

Optionally, the core network device is an access and mobility management function (Access and Mobility Management Function, AMF) network element and/or a session management function (Session Management Function, SMF) network element.

As an optional embodiment, the first PDU session establishment request message or the first PDU session modification request message includes at least one of the following:

a first non-3 GPP access indication for indicating to establish a PDU session or QoS flow for the non-3 GPP device;

identification information of non-3 GPP devices; when only the identification information of the non-3 GPP equipment is included, the identification information of the non-3 GPP equipment is equivalent to a first non-3 GPP access instruction, namely, the implicit instruction establishes PDU session or QoS flow for the non-3 GPP equipment;

a data network name DNN requesting establishment or request of a modified PDU session;

network slice identification of a PDU session requested to be established or modified.

As another optional embodiment, the first PDU session establishment response message or the first PDU session modification response message includes: a second non-3 GPP access indication for indicating a successful establishment of a PDU session or QoS flow for the non-3 GPP device.

In at least one embodiment of the present application, step 201 includes:

the terminal equipment acquires a session policy of the non-3 GPP equipment from a local configuration;

or alternatively, the process may be performed,

and the terminal equipment acquires the session policy of the non-3 GPP equipment from the core network equipment.

In other words, the session policy of the non-3 GPP device may be configured in the terminal device, e.g. pre-configured by the operator or owner or user of the terminal device. Alternatively, the session policy of the non-3 GPP device is obtained by the terminal device from the core network device.

In at least one optional embodiment of the application, the terminal device obtaining a session policy of the non-3 GPP device from a core network device, comprises:

the terminal equipment acquires the session policy of the non-3 GPP equipment in a PDU session establishment flow or a PDU session modification flow of the terminal equipment;

or alternatively, the process may be performed,

and the terminal equipment acquires the session policy of the non-3 GPP equipment in the registration process of the terminal equipment.

As an optional embodiment, the terminal device obtains the session policy of the non-3 GPP device in a PDU session establishment procedure or a PDU session modification procedure of the terminal device, including:

the terminal device sends a second PDU session establishment request message or a second PDU session modification request message to the core network device, where the second PDU session establishment request message is used to request to establish a PDU session of the terminal device, and the second PDU session modification request message is used to request to modify the PDU session of the terminal device, for example, to establish a QoS flow of the terminal device, or to modify a parameter of the PDU session of the terminal device, or to request a session policy of a non-3 GPP device;

the terminal equipment receives a second PDU session establishment response message or a second PDU session modification response message sent by the core network equipment; the second PDU session establishment response message is used for indicating the PDU session of the terminal equipment to be successfully established; the second PDU session modification response message is used for indicating the PDU session of the terminal equipment to be successfully modified;

wherein the second PDU session establishment response message or the second PDU session modification response message carries a session policy of the non-3 GPP device.

Optionally, the second PDU session establishment request message or the second PDU session modification request message includes at least one of the following:

a third non-3 GPP access indication for indicating that the terminal equipment has the capability of non-3 GPP equipment access;

identification information of the terminal device.

It should be noted that, the identification information of the terminal device may also be used as an example of the third non-3 GPP access indication, that is, the identification information of the terminal device implicitly indicates that the terminal device has the capability of accessing the non-3 GPP device.

As another optional embodiment, the terminal device obtains a session policy of the non-3 GPP device during a registration process of the terminal device, including:

the terminal equipment sends a registration request message to core network equipment, wherein the registration request message is used for requesting registration to a 5G system;

and the terminal equipment receives a registration response message sent by the core network equipment, wherein the registration response message carries a session policy of the non-3 GPP equipment.

Optionally, the registration request message includes at least one of:

identification information of the terminal device.

It should be noted that, the identification information of the terminal device may also be used as an example of the third non-3 GPP access indication; i.e. the identification information of the terminal device implicitly indicates that the terminal device has the capability of non-3 GPP device access.

In at least one optional embodiment of the application, the identification information of the non-3 GPP device comprises at least one of:

an equipment identity of the non-3 GPP equipment;

a connection identifier of the non-3 GPP device;

and the type identification of the non-3 GPP equipment.

Wherein the device identification of the non-3 GPP device includes at least one of:

a MAC address of the non-3 GPP device;

an international mobile subscriber identity IMSI of the non-3 GPP device;

a user permanent identifier, SUPI, of the non-3 GPP device;

a user temporary identifier, sui, of the non-3 GPP device;

the general public user identity GPSI of the non-3 GPP device.

Wherein the connection identifier of the non-3 GPP device includes at least one of:

-a service set identification (Service Set Identifier, SSID) of the non-3 GPP device connection terminal device;

the non-3 GPP device connects access technologies (e.g., wiFi, wire, bluetooth, etc.) used by the terminal device;

the non-3 GPP device connects interface information (e.g., virtual interface or physical interface) of the terminal device.

Wherein the type identification of the non-3 GPP device includes at least one of:

service identification required by the non-3 GPP equipment;

service requirement information of the non-3 GPP equipment;

and the identification of the group to which the non-3 GPP device belongs.

It should be noted that, in the embodiment of the present application, the type identifier of the non-3 GPP device may be set in the terminal device, or the type identifier of the non-3 GPP device may be set manually, which is not limited herein.

Alternatively, multiple non-3 GPP devices may use different identification information of the non-3 GPP devices, or may use the same identification information of the non-3 GPP devices (it may also be understood that the multiple non-3 GPP devices belong to the same group).

In summary, in the embodiment of the present application, for a non-3 GPP device accessing a 5G system through a terminal device, the terminal device requests a core network device to establish a PDU session and/or QoS flow for a corresponding non-3 GPP device, so that the core network device performs differentiated QoS management on the non-3 GPP device accessed from the terminal device; because different non-3 GPP devices may have different service requirements, the same non-3 GPP device may also have different service requirements, and the embodiment of the application can provide proper QoS support according to different service requirements, thereby not only meeting the service requirements of the device, but also reasonably using the resources of 5 GS.

As shown in fig. 3, an embodiment of the present application further provides a method for establishing a session channel of a non-3 GPP device, including:

step 301, core network equipment acquires a session policy of non-3 GPP equipment;

Step 302, the core network device establishes a session channel for the non-3 GPP device according to the session policy of the non-3 GPP device and the request of the terminal device; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

It should be noted that, in the embodiment of the present application, the terminal device may be a 3GPP terminal device, or a home gateway, which is not specifically limited herein.

identification information of one or more non-3 GPP devices using one QoS flow;

establishment parameters of session channels.

Wherein the session channel establishment parameters include at least one of:

an IP type;

an Ethernet type;

a business continuity mode;

a control surface channel;

a user plane channel;

a data network name DNN of the session channel;

network slice identification of the session channel.

In at least one embodiment of the present application, step 301 comprises:

the core network device obtains a locally stored session policy of the non-3 GPP device;

or alternatively, the process may be performed,

the core network device obtains the session policy of the non-3 GPP device from a unified data management UDM network element or a policy control function PCF network element.

In other words, the session policy of the non-3 GPP device may be configured in the core network device. Alternatively, the session policy of the non-3 GPP device is obtained by the core network device from a UDM network element or a PCF network element.

The session policy may or may not be associated with a particular terminal device. In other words, different terminal devices may use different session policies, or different terminal devices may use the same session policies.

Optionally, the core network device may obtain the session policy of the non-3 GPP device from the UDM network element or the PCF network element after receiving the request of the terminal device.

For example, the terminal device sends a registration request to the core network device, where the registration request message includes at least one of: a third non-3 GPP access indication for indicating that the terminal equipment has the capability of non-3 GPP equipment access; identification information of the terminal device. The core network device sends at least one of the third non-3 GPP access indication and the identification information of the terminal device to the UDM/PCF; the UDM/PCF sends the session policy of the non-3 GPP device to the core network device. It should be noted that, the identification information of the terminal device may also be used as an example of the third non-3 GPP access indication; i.e. the identification information of the terminal device implicitly indicates that the terminal device has the capability of non-3 GPP device access.

For another example, the terminal device sends a PDU session establishment request or a PDU session modification request to the core network device, where the PDU session establishment request or the PDU session modification request includes at least one of the following: a third non-3 GPP access indication for indicating that the terminal equipment has the capability of non-3 GPP equipment access; identification information of the terminal device. The core network device sends at least one of the third non-3 GPP access indication and the identification information of the terminal device to the UDM/PCF; the UDM/PCF sends the session policy of the non-3 GPP device to the core network device. It should be noted that, the identification information of the terminal device may also be used as an example of the third non-3 GPP access indication; i.e. the identification information of the terminal device implicitly indicates that the terminal device has the capability of non-3 GPP device access.

For another example, the core network device directly sends the identification information of the terminal device to the UDM/PCF; and the UDM/PCF determines that the terminal equipment has the capacity of accessing the non-3 GPP equipment according to the identification information of the terminal equipment, and sends the session policy of the non-3 GPP equipment to the core network equipment. It should be noted that, the identification information of the terminal device may also be used as an example of the third non-3 GPP access indication; i.e. the identification information of the terminal device implicitly indicates that the terminal device has the capability of non-3 GPP device access.

Further, the method further comprises:

and the core network equipment sends the session policy of the non-3 GPP equipment to the terminal equipment.

In at least one embodiment of the present application, the core network device sends the session policy of the non-3 GPP device to a terminal device, including:

the core network device sends the session policy of the non-3 GPP device to the terminal device in a PDU session establishment flow or a PDU session modification flow of the terminal device;

or alternatively, the process may be performed,

and the core network equipment sends the session policy of the non-3 GPP equipment to the terminal equipment in the registration process of the terminal equipment.

Optionally, the terminal device carries at least one of a third non-3 GPP access indication and identification information of the terminal device in a PDU session establishment procedure or a PDU session modification procedure or a registration procedure, so as to indicate that the terminal device has a capability of accessing the non-3 GPP device; the core network device then transmits the session policy of the non-3 GPP device to the terminal device in the PDU session establishment procedure or PDU session modification procedure or registration procedure.

As an optional embodiment, the core network device sends the session policy of the non-3 GPP device to the terminal device in a PDU session establishment procedure or a PDU session modification procedure of the terminal device, including:

The core network device receives a second PDU session establishment request message or a second PDU session modification request message sent by the terminal device, where the second PDU session establishment request message is used to request establishment of a PDU session of the terminal device, and the second PDU session modification request message is used to request modification of the PDU session of the terminal device;

the core network device sends a second PDU session establishment response message or a second PDU session modification response message to the terminal device; the second PDU session establishment response message is used for indicating the PDU session of the terminal equipment to be successfully established; the second PDU session modification response message is used for indicating successful PDU session modification of the terminal equipment;

Wherein the second PDU session establishment request message or the second PDU session modification request message includes at least one of:

identification information of the terminal device.

As another optional embodiment, the core network device sends the session policy of the non-3 GPP device to the terminal device during the registration of the terminal device, including:

The method comprises the steps that an access and mobility management function (AMF) network element receives a registration request message sent by a terminal device, wherein the registration request message is used for requesting registration to a 5G system;

the AMF sends a registration response message to the terminal equipment, wherein the registration response message carries the session policy of the non-3 GPP equipment.

Wherein the registration request message includes at least one of:

identification information of the terminal device.

As an optional embodiment, the core network device establishes a session channel for the non-3 GPP device according to a session policy of the non-3 GPP device and a request of a terminal device, including:

the core network device receives a first PDU session establishment request message or a first PDU session modification request message sent by the terminal device, where the first PDU session establishment request message is used to request establishment of a PDU session for the non-3 GPP device, and the first PDU session modification request message is used to request establishment of a QoS stream for the non-3 GPP device;

the core network device establishes PDU session or QoS stream for the non-3 GPP device according to the first PDU session establishment request message or the first PDU session modification request message;

The core network device sends a first PDU session establishment response message or a first PDU session modification response message to the terminal device; the first PDU session establishment response message is used for indicating successful establishment of PDU session of the non-3 GPP equipment; the first PDU session modification response message is used for indicating successful establishment of QoS flow of the non-3 GPP equipment.

Wherein the first PDU session establishment request message or the first PDU session modification request message includes at least one of the following:

the identification information of the non-3 GPP equipment is equivalent to the first non-3 GPP access indication when only the identification information of the non-3 GPP equipment is included, namely the PDU session or QoS flow is established for the non-3 GPP equipment by the implicit indication;

an equipment identity of the non-3 GPP equipment;

a connection identifier of the non-3 GPP device;

and the type identification of the non-3 GPP equipment.

a MAC address of the non-3 GPP device;

an international mobile subscriber identity IMSI of the non-3 GPP device;

a user permanent identifier, SUPI, of the non-3 GPP device;

a user temporary identifier, sui, of the non-3 GPP device;

the general public user identity GPSI of the non-3 GPP device.

service identification required by the non-3 GPP equipment;

service requirement information of the non-3 GPP equipment;

And the identification of the group to which the non-3 GPP device belongs.

Alternatively, multiple non-3 GPP devices may use different identification information of the non-3 GPP devices, or may use the same identification information of the non-3 GPP devices (e.g., it may be understood that the multiple non-3 GPP devices belong to the same group).

In order to better describe the session channel establishment method of the non-3 GPP device provided by the embodiment of the present application, the following description is made with reference to several examples.

For example one, a terminal device (e.g., 5G-RG) requests establishment of a PDU session for a non-3 GPP device. The 5G-RG carries the group identification of the non-3 GPP equipment in the PDU session establishment request, and the network side establishes PDU session for the non-3 GPP equipment according to the corresponding session policy of the group. Session policies may exist in the SMF or in the PCF. As shown in fig. 4:

step 40,5G-RG obtains the identification information of the non-3 GPP device.

The identification information of the non-3 GPP device may be at least one of:

the device identification of the non-3 GPP device may include, for example, at least one of: a MAC address of a non-3 GPP device, an IMSI of a non-3 GPP device, a SUPI of a non-3 GPP device, a sui of a non-3 GPP device, or a GPSI of a non-3 GPP device;

the connection identity of the non-3 GPP device may include, for example, at least one of: a service set identification (Service Set Identifier, SSID) of the non-3 GPP device connection 5G-RG, an access technology (e.g., wiFi, wired, bluetooth, etc.) used by the non-3 GPP device connection 5G-RG, interface information (e.g., virtual interface or physical interface) of the non-3 GPP device connection 5G-RG;

the type information of the non-3 GPP device may include, for example, at least one of: the service identifier that the non-3 GPP device needs to use, and the identifier of the group to which the non-3 GPP device belongs. Wherein the type information of the non-3 GPP device may be set in the 5G-RG, or by manual setting, etc.

The 5G-RG can acquire the identification information of the non-3 GPP equipment through the connection establishment process between the non-3 GPP equipment and the 5G-RG.

Step 41,5G-RG sends a non-access stratum NAS message to AMF requesting establishment of PDU session for non-3 GPP device.

Optionally, the NAS message carries a first non-3 GPP access indication, which indicates that a PDU session is established for the non-3 GPP device. The first non-3 GPP access indication may also be, for example, identification information of the non-3 GPP device.

Optionally, the NAS message carries a PDU session establishment request message, and establishes a PDU session for the non-3 GPP device. Optionally, the PDU session establishment request message may carry a first non-3 GPP access indication, which indicates that a PDU session is established for the non-3 GPP device.

Optionally, the 5G-RG carries DNN and/or S-NSSAI in NAS message for establishing PDU session for the non-3 GPP device.

Optionally, the AMF selects an SMF with a capability of establishing a PDU session for the non-3 GPP device according to the first non-3 GPP access indication carried in the NAS message.

In step 42, the amf sends an N11 message to the SMF to establish a PDU session for the non-3 GPP device. The N11 message may include a first non-3 GPP access indication.

Optionally, the N11 message includes a PDU session establishment request message, where the PDU session establishment request message may carry a first non-3 GPP access indication.

Step 43, the smf sends a first non-3 GPP access indication to the UDM/PCF.

Illustratively, the SMF sends a nudm_sdm_get or nudm_sdm_subscribe or nudm_sdm_get request to the UDM, carrying a first non-3 GPP access indication.

Illustratively, the SMF carries an access indication of the non-3 GPP device in the set-up or modification request of SM Policy Association. For example, the SMF sends to the PCF an npcf_smpolicy control_create or npcf_smpolicy control_update request, carrying the first non-3 GPP access indication.

In step 44, the udm/PCF sends the SMF the session policy of the non-3 GPP device.

Illustratively, the UDM sends a nudm_sdm_get or nudm_sdm_subscnibe response to the SMF, carrying the session policy of the non-3 GPP device.

Illustratively, the PCF sends the session policy of the non-3 GPP device to the SMF during the set-up or modification of SM Policy Association. For example, the PCF sends to the SMF either an npcf_smpolicy control_create or an npcf_smpolicy control_update response, which carries the session policy of the non-3 GPP device.

By way of example, the session policy of the non-3 GPP device can include QoS policies, charging policies, etc. for traffic flows of the non-3 GPP device.

The non-3 GPP device refers to a non-3 GPP device indicated by the identification information of the non-3 GPP device.

Step 45, an N4 session of the PDU session is established between the smf and the UPF.

Illustratively, the SMF generates N4 rules according to the session policy of the non-3 GPP device, and sends the N4 rules to the UPF to control the traffic forwarding of the PDU session, and implement the QoS policy.

Step 46, the smf sends a response message of the N11 message to the AMF, indicating that the PDU session of the non-3 GPP device was successfully established.

Optionally, the response message of the N11 message may include a second non-3 GPP access indication.

Illustratively, the response message of the N11 message includes a PDU session establishment response message. The PDU session establishment request message may carry a second non-3 GPP access indication.

In step 47, the AMF sends a NAS message to the 5G-RG indicating that the PDU session of the non-3 GPP device was successfully established.

Optionally, the NAS message carries a second non-3 GPP access indication, which indicates that the PDU session is successfully established for the non-3 GPP device.

The NAS message includes a PDU session establishment response message, for example. Optionally, the PDU session establishment response message may carry a second non-3 GPP access indication, which indicates that the non-3 GPP device successfully establishes a PDU session.

The PDU session establishment procedure is described above as an example. The 5G-RG may also request to establish QoS flows for non-3 GPP devices. At this time, the 5G-RG may send PDU session modification request, and the network side establishes QoS flow for the non-3 GPP device according to the session policy corresponding to the access instruction of the non-3 GPP device. The PDU session establishment request in steps 41 and 42 may be replaced with a PDU session modification request, the N4 session establishment in step 45 may be replaced with an N4 session modification, and the PDU session establishment response in steps 46 and 47 may be replaced with a PDU session modification response.

It should be noted that the non-3 GPP session policy may be configured in the 5G-RG (e.g., configured by an operator or owner or user of the 5G-RG), or may be obtained through example two or example three.

The second example, the 5G-RG acquires the session policy of the non-3 GPP equipment in the PDU session establishment process; as shown in fig. 5:

step 51,5G-RG sends NAS message to AMF requesting to establish PDU session.

Optionally, the NAS message includes a third non-3 GPP access indication, which indicates that the 5G-RG has a capability of non-3 GPP device access.

The third non-3 GPP access indication may be a displayed indication or an implicit indication, for example, an indication by the identification information of the 5G-RG.

Illustratively, the NAS message carries a PDU session establishment request message. Optionally, the PDU session establishment request message may carry an access indication of the non-3 GPP device, which indicates that the PDU session is established for the non-3 GPP device.

Optionally, the NAS message may further include identification information of the non-3 GPP device. For example, when the 5G-RG has knowledge of the non-3 GPP identification information, it can be carried in the NAS message. It is worth noting that at this point the non-3 GPP device may have already established a connection with the 5G-RG or may not have established a connection with the 5G-RG. For example, the 5G-RG knows the identification information of the non-3 GPP devices to which it can be connected according to the local configuration.

The amf sends an N11 message to the SMF requesting the PDU session to be established, step 52.

Optionally, the N11 message includes a third non-3 GPP access indication.

Optionally, the N11 message includes identification information of the non-3 GPP device.

For example, the N11 message includes a PDU session establishment request message, where the PDU session establishment request message may carry a third non-3 GPP access indication, or identification information of a non-3 GPP device.

Step 53, the smf sends a third non-3 GPP access indication to the UDM/PCF.

Optionally, the SMF also sends identification information of the non-3 GPP device to the UDM/PCF.

Illustratively, the SMF sends a nudm_sdm_get or nudm_sdm_subscribe or nudm_sdm_get request to the UDM, where the request carries the third non-3 GPP access indication or identification information of the non-3 GPP device.

Illustratively, the SMF carries the non-3 GPP device access indication in the setup or modification request of SM Policy Association. For example, the SMF sends an npcf_smpolicy control_create or an npcf_smpolicy control_update request to the PCF, where the request carries the third non-3 GPP access indication or identification information of the non-3 GPP device.

In step 54, the udm/PCF sends the SMF a session policy for the non-3 GPP device.

The session policy of the non-3 GPP device is used to describe how to establish a session channel for the non-3 GPP device. The session policy of the non-3 GPP device includes at least one of:

identification information of one or more non-3 GPP devices using one QoS flow.

Optionally, the session policy of the non-3 GPP device may further include a session channel establishment parameter. The session channel setup parameters may be used to indicate that different types of session channels are set up, for example, PDU sessions are set up for user plane channels (data is transferred using user plane, e.g. using air interface user plane and N3 user plane channels), PDU sessions for control plane channels (data is transferred using control plane signaling, e.g. NAS messaging using terminal devices), optimized CP plane PDU sessions (i.e. data is transferred using control plane and user plane, e.g. air interface user plane, control plane is used between RAN and core network), IP type PDU sessions, ethernet type PDU sessions), service continuity modes are SSC mode 1 or 2 or 3 PDU sessions.

The session policy of the non-3 GPP device described above may also be obtained from the local configuration of the SMF.

It should be noted that, when the third non-3 GPP access indication is an implicit indication, for example, is the identification information of the 5G-RG, optionally, the UDM/PCF may determine that the 5G-RG has the non-3 GPP access capability according to the subscription data of the 5G-RG, so as to send the session policy of the non-3 GPP device to the SMF.

Step 55, an N4 session of the PDU session is established between the smf and the UPF.

Illustratively, the SMF generates an N4 rule according to the session policy of the 5G-RG, and sends the N4 rule to the UPF to control the traffic forwarding of the PDU session, and implement the QoS policy.

The session policy for 5G-RG can be obtained from UDM/PCF or from the local configuration of SMF.

At step 56, the smf sends a response message to the AMF for the N11 message indicating that the PDU session was successfully established.

Illustratively, the response message of the N11 message includes a PDU session establishment response message.

In step 57, the AMF sends a NAS message to the 5G-RG indicating that the PDU session was successfully established.

Optionally, the NAS message carries a session policy of the non-3 GPP device.

It should be noted that the 5G-RG can establish a session channel for the non-3 GPP device according to the session policy request of the non-3 GPP device. The 5G-RG can request to establish a session channel when the non-3 GPP equipment identification information connected to the 5G-RG is acquired subsequently; session channels may also be established in advance for non-3 GPP devices. In the latter case, the non-3 GPP device can use the pre-established session channel directly for traffic transmission after being connected to the 5G-RG. How the 5G-RG requests to establish a session channel for a non-3 GPP device may refer to the description of example one.

It should be noted that the 5G-RG may also request the session policy of the non-3 GPP device in the PDU session modification procedure. The 5G-RG can send a PDU session modification request at this time. The PDU session establishment request in steps 51 and 52 may be replaced with a PDU session modification request, the N4 session establishment in step 55 may be replaced with an N4 session modification, and the PDU session establishment response in steps 56 and 57 may be replaced with a PDU session modification response.

Example three, the 5G-RG acquires session policy of the non-3 GPP device during registration, as shown in fig. 6:

step 61,5G-RG sends a registration request message to AMF requesting registration to the 5G system.

Optionally, the registration request message includes a third non-3 GPP access indication, which indicates that the 5G-RG has a capability of non-3 GPP device access.

Optionally, the registration request message may further include identification information of the non-3 GPP device.

The amf sends a third non-3 GPP access indication to the UDM/PCF, step 62.

Optionally, the AMF also sends identification information of the non-3 GPP device to the UDM/PCF.

Illustratively, the AMF sends a nudm_uecm_registration or nudm_sdm_get request to the UDM carrying at least one of a non-third non-3 GPP access indication and identification information of the non-3 GPP device.

Illustratively, the AMF carries at least one of the third non-3 GPP access indication and the identification information of the non-3 GPP device in the establishment or modification request of AM Policy Association. For example, the AMF sends to the PCF an npcf_ampoliccontrol_create or an npcf_ampoliccontrol_update request carrying at least one of a third non-3 GPP access indication and identification information of the non-3 GPP device.

Step 63, the udm/PCF sends the session policy of the non-3 GPP device to the AMF. The session policy of the non-3 GPP device in this step may exemplify the description of the session policy of the non-3 GPP device in the second example.

Illustratively, the UDM sends a nudm_uecm_registration or nudm_sdm_get response to the AMF, carrying the session policy of the non-3 GPP device.

Illustratively, the PCF sends the session policy of the non-3 GPP device to the AMF during the set-up or modification of AM Policy Association. For example, the PCF sends an npcf_ampoliccontrol_create or npcf_ampoliccontrol_update response to the AMF, carrying the session policy of the non-3 GPP device.

Optionally, the UDM/PCF determines, according to subscription data and/or operator configuration information of the terminal device, that the 5G-RG can allow access to non-3 GPP devices.

In step 64, the amf sends a registration response message to the 5G-RG, carrying the session policy of the non-3 GPP device.

It should be noted that this example describes the procedure of the 5G-RG obtaining the non-3 GPP device session policy from the network side using the registration procedure as an example. In practical use, the 5G-RG can also acquire the session policy of the non-3 GPP equipment through other flows interacted with the network side. For example, the terminal device configuration update procedure and the like are not enumerated here.

According to the method for establishing the session channel of the non-3 GPP equipment, provided by the embodiment of the application, the executive body can be the device for establishing the session channel of the non-3 GPP equipment. In the embodiment of the present application, a method for executing a session channel establishment method of a non-3 GPP device by a session channel establishment device of a non-3 GPP device is taken as an example, and the session channel establishment device of a non-3 GPP device provided by the embodiment of the present application is described.

As shown in fig. 7, an embodiment of the present application further provides a session channel establishment apparatus 700 of a non-3 GPP device, including:

a first obtaining module 701, configured to obtain a session policy of a non-3 GPP device;

a request establishing module 702, configured to request, according to a session policy of the non-3 GPP device, a core network device to establish a session channel for the non-3 GPP device; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

As an optional embodiment, the session policy of the non-3 GPP device further comprises at least one of:

identification information of one or more non-3 GPP devices using one QoS flow;

establishment parameters of session channels.

As an optional embodiment, the session channel establishment parameters include at least one of:

an IP type;

an Ethernet type;

a business continuity mode;

a control surface channel;

a user plane channel;

a data network name DNN of the session channel;

network slice identification of the session channel.

As an alternative embodiment, the first obtaining module includes:

a first obtaining sub-module, configured to obtain a session policy of the non-3 GPP device from a local configuration;

or alternatively, the process may be performed,

and the second acquisition sub-module is used for acquiring the session policy of the non-3 GPP equipment from the core network equipment.

As an alternative embodiment, the apparatus further comprises:

a third obtaining module, configured to obtain identification information of a non-3 GPP device;

the request establishing module includes:

and the request establishing sub-module is used for requesting the core network equipment to establish a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment and the identification information of the non-3 GPP equipment.

As an alternative embodiment, the request building sub-module includes:

a first sending unit, configured to send a first PDU session establishment request message or a first PDU session modification request message to a core network device according to a session policy of the non-3 GPP device and identification information of the non-3 GPP device, where the first PDU session establishment request message is used to request establishment of a PDU session for the non-3 GPP device, and the first PDU session modification request message is used to request establishment of a QoS flow for the non-3 GPP device;

a first receiving unit, configured to receive a first PDU session establishment response message or a first PDU session modification response message sent by the core network device; the first PDU session establishment response message is used for indicating successful establishment of PDU session of the non-3 GPP equipment; the first PDU session modification response message is used for indicating successful establishment of QoS flow of the non-3 GPP equipment.

identification information of the non-3 GPP device,

As an optional embodiment, the first PDU session establishment response message or the first PDU session modification response message includes: a second non-3 GPP access indication for indicating a successful establishment of a PDU session or QoS flow for the non-3 GPP device.

As an alternative embodiment, the second obtaining submodule includes:

a first obtaining unit, configured to obtain a session policy of the non-3 GPP device in a PDU session establishment procedure or a PDU session modification procedure of the terminal device;

or alternatively, the process may be performed,

and the second acquisition unit is used for acquiring the session policy of the non-3 GPP equipment in the registration process of the terminal equipment.

As an alternative embodiment, the first obtaining unit is further configured to:

sending a second PDU (protocol data unit) session establishment request message or a second PDU session modification request message to core network equipment, wherein the second PDU session establishment request message is used for requesting to establish a PDU session of the terminal equipment, and the second PDU session modification request message is used for requesting to establish a QoS (quality of service) stream of the terminal equipment;

Receiving a second PDU session establishment response message or a second PDU session modification response message sent by the core network device; the second PDU session establishment response message is used for indicating the PDU session of the terminal equipment to be successfully established; the second PDU session modification response message is used for indicating successful PDU session modification of the terminal equipment;

As an optional embodiment, the second PDU session establishment request message or the second PDU session modification request message includes at least one of the following:

identification information of the terminal device.

As an alternative embodiment, the second obtaining unit is further configured to:

a registration request message is sent to core network equipment, and the registration request message is used for requesting registration to a 5G system;

and receiving a registration response message sent by the core network equipment, wherein the registration response message carries a session policy of the non-3 GPP equipment.

As an alternative embodiment, the registration request message includes at least one of:

identification information of the terminal device.

As an optional embodiment, the identification information of the non-3 GPP device includes at least one of:

an equipment identity of the non-3 GPP equipment;

a connection identifier of the non-3 GPP device;

and the type identification of the non-3 GPP equipment.

As an optional embodiment, the device identification of the non-3 GPP device includes at least one of:

a MAC address of the non-3 GPP device;

an international mobile subscriber identity IMSI of the non-3 GPP device;

a user permanent identifier, SUPI, of the non-3 GPP device;

a user temporary identifier, sui, of the non-3 GPP device;

the general public user identity GPSI of the non-3 GPP device.

As an optional embodiment, the connection identifier of the non-3 GPP device includes at least one of:

the non-3 GPP equipment is connected with a service set identifier of the terminal equipment;

the non-3 GPP equipment is connected with an access technology used by the terminal equipment;

the non-3 GPP equipment is connected with interface information of the terminal equipment.

As an alternative embodiment, the type identification of the non-3 GPP device includes at least one of:

Service identification required by the non-3 GPP equipment;

service requirement information of the non-3 GPP equipment;

and the identification of the group to which the non-3 GPP device belongs.

It should be noted that, the session channel establishment device of the non-3 GPP device provided by the embodiment of the present application is a device capable of executing the session channel establishment method of the non-3 GPP device, and all embodiments of the session channel establishment method of the non-3 GPP device are applicable to the device, and the same or similar beneficial effects can be achieved.

As shown in fig. 8, an embodiment of the present application further provides a session channel establishment apparatus 800 of a non-3 GPP device, including:

A second obtaining module 801, configured to obtain a session policy of a non-3 GPP device;

an establishing module 802, configured to establish a session channel for the non-3 GPP device according to a session policy of the non-3 GPP device and a request of a terminal device; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

identification information of one or more non-3 GPP devices using one QoS flow;

establishment parameters of session channels.

an IP type;

an Ethernet type;

a business continuity mode;

a control surface channel;

a user plane channel;

a data network name DNN of the session channel;

Network slice identification of the session channel.

As an alternative embodiment, the second obtaining module includes:

a third obtaining sub-module, configured to obtain a locally stored session policy of the non-3 GPP device;

or alternatively, the process may be performed,

and the fourth acquisition sub-module is used for acquiring the session policy of the non-3 GPP equipment from the Unified Data Management (UDM) network element or the Policy Control Function (PCF) network element.

As an alternative embodiment, the apparatus further comprises:

and the strategy sending module is used for sending the session strategy of the non-3 GPP equipment to the terminal equipment.

As an alternative embodiment, the policy sending module includes:

a first policy sending sub-module, configured to send a session policy of the non-3 GPP device to the terminal device in a PDU session establishment procedure or a PDU session modification procedure of the terminal device;

or alternatively, the process may be performed,

and the second policy sub-module is used for sending the session policy of the non-3 GPP equipment to the terminal equipment in the registration process of the terminal equipment.

As an alternative embodiment, the first policy sending submodule is further configured to:

receiving a second PDU (protocol data unit) session establishment request message or a second PDU session modification request message sent by a terminal device, wherein the second PDU session establishment request message is used for requesting to establish a PDU session of the terminal device, and the second PDU session modification request message is used for requesting to modify the PDU session of the terminal device;

Sending a second PDU session establishment response message or a second PDU session modification response message to the terminal device; the second PDU session establishment response message is used for indicating the PDU session of the terminal equipment to be successfully established; the second PDU session modification response message is used for indicating successful PDU session modification of the terminal equipment;

identification information of the terminal device.

receiving a registration request message sent by a terminal device, wherein the registration request message is used for requesting registration to a 5G system;

and sending a registration response message to the terminal equipment, wherein the registration response message carries the session policy of the non-3 GPP equipment.

identification information of the terminal device.

As an alternative embodiment, the establishing module includes:

a third receiving sub-module, configured to receive a first PDU session establishment request message or a first PDU session modification request message sent by the terminal device, where the first PDU session establishment request message is used to request establishment of a PDU session for the non-3 GPP device, and the first PDU session modification request message is used to request establishment of a QoS flow for the non-3 GPP device;

a first establishing sub-module, configured to establish a PDU session or QoS flow for the non-3 GPP device according to the first PDU session establishment request message or the first PDU session modification request message;

a third sending submodule, configured to send a first PDU session establishment response message or a first PDU session modification response message to the terminal device; the first PDU session establishment response message is used for indicating successful establishment of PDU session of the non-3 GPP equipment; the first PDU session modification response message is used for indicating successful establishment of QoS flow of the non-3 GPP equipment.

identification information of the non-3 GPP device,

The session channel establishment device of the non-3 GPP device in the embodiment of the present application may be an electronic device, for example, an electronic device with an operating system, or may be a component in the electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. By way of example, terminals may include, but are not limited to, the types of terminals 11 listed above, other devices may be servers, network attached storage (Network Attached Storage, NAS), etc., and embodiments of the application are not specifically limited.

The session channel establishment device of the non-3 GPP device provided by the embodiment of the present application can implement each process implemented by the method embodiments of fig. 1 to fig. 6, and achieve the same technical effects, and in order to avoid repetition, a detailed description is omitted here.

Optionally, as shown in fig. 9, the embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, where the memory 902 stores a program or instructions that can be executed on the processor 901, for example, when the communication device 900 is a terminal device, the program or instructions implement, when executed by the processor 901, the steps of the session channel establishment method embodiment of the non-3 GPP device, and achieve the same technical effects. When the communication device 900 is a network side device, the program or the instruction, when executed by the processor 901, implements each step of the session channel establishment method embodiment of the non-3 GPP device, and can achieve the same technical effects, so that repetition is avoided, and no further description is given here.

The embodiment of the application also provides the terminal equipment, which comprises a processor and a communication interface, wherein the communication interface is used for acquiring the session policy of the non-3 GPP equipment; the processor is used for requesting the core network equipment to establish a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow. The terminal embodiment corresponds to the terminal-side method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the terminal embodiment, and the same technical effects can be achieved. Specifically, fig. 10 is a schematic hardware structure of a terminal device for implementing an embodiment of the present application.

The terminal device 1000 includes, but is not limited to: at least some of the components of the radio frequency unit 1001, the network module 1002, the audio output unit 1003, the input unit 1004, the sensor 1005, the display unit 1006, the user input unit 1007, the interface unit 1008, the memory 1009, and the processor 1010, etc.

Those skilled in the art will appreciate that terminal 1000 can also include a power source (e.g., a battery) for powering the various components, which can be logically connected to processor 10 by a power management system so as to perform functions such as managing charge, discharge, and power consumption by the power management system. The terminal structure shown in fig. 10 does not constitute a limitation of the terminal, and the terminal may include more or less components than shown, or may combine some components, or may be arranged in different components, which will not be described in detail herein.

It should be appreciated that in embodiments of the present application, the input unit 1004 may include a graphics processing unit (Graphics Processing Unit, GPU) 10041 and a microphone 10042, where the graphics processor 10041 processes image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 1007 includes at least one of a touch panel 10071 and other input devices 10072. The touch panel 10071 is also referred to as a touch screen. The touch panel 10071 can include two portions, a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and so forth, which are not described in detail herein.

In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 1001 may transmit the downlink data to the processor 1010 for processing; in addition, the radio frequency unit 1001 may send uplink data to the network side device. In general, the radio frequency unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.

The memory 1009 may be used to store software programs or instructions and various data. The memory 1009 may mainly include a first memory area storing programs or instructions and a second memory area storing data, wherein the first memory area may store an operating system, application programs or instructions (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. Further, the memory 1009 may include volatile memory or nonvolatile memory, or the memory 1009 may include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM), static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (ddr SDRAM), enhanced SDRAM (Enhanced SDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). Memory 1009 in embodiments of the application includes, but is not limited to, these and any other suitable types of memory.

The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor that primarily processes operations involving an operating system, user interface, application programs, and the like, and a modem processor that primarily processes wireless communication signals, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 1010.

The radio frequency unit 1001 is configured to obtain a session policy of a non-3 GPP device;

a processor 1010, configured to request, according to a session policy of the non-3 GPP device, a core network device to establish a session channel for the non-3 GPP device; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow.

In the embodiment of the application, aiming at the non-3 GPP equipment accessed to the 5G system through the terminal equipment, the terminal equipment requests the core network equipment to establish PDU session and/or QoS flow for the corresponding non-3 GPP equipment, thereby leading the core network equipment to carry out differentiated QoS management on the non-3 GPP equipment accessed from the terminal equipment.

It should be noted that, if the terminal device provided in the embodiment of the present application is a terminal device capable of executing the method for establishing a session channel of the non-3 GPP device, all embodiments of the method for establishing a session channel of the non-3 GPP device are applicable to the terminal device, and the same or similar beneficial effects can be achieved.

The embodiment of the application also provides a network side device, which comprises a processor and a communication interface, wherein the communication interface is used for acquiring the session policy of the non-3 GPP device; the processor is used for establishing a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment and the request of the terminal equipment; the session channel includes: protocol data unit, PDU, session, and/or quality of service, qoS, flow. The network side device embodiment corresponds to the network side device method embodiment, and each implementation process and implementation manner of the method embodiment can be applied to the network side device embodiment, and the same technical effects can be achieved.

Specifically, the embodiment of the application also provides network side equipment. As shown in fig. 11, the network side device 1100 includes: a processor 1101, a network interface 1102, and a memory 1103. The network interface 1102 is, for example, a common public radio interface (common public radio interface, CPRI).

Specifically, the network side device 1100 of the embodiment of the present application further includes: instructions or programs stored in the memory 1103 and capable of running on the processor 1101, the processor 1101 calls the instructions or programs in the memory 1103 to execute the method executed by each module shown in fig. 8, and achieve the same technical effects, so that repetition is avoided, and therefore, the description is omitted herein.

The embodiment of the application also provides a readable storage medium, on which a program or an instruction is stored, which when executed by a processor, implements each process of the session channel establishment method embodiment of the non-3 GPP device, and can achieve the same technical effect, so that repetition is avoided, and no further description is given here.

Wherein the processor is a processor in the terminal described in the above embodiment. The readable storage medium includes computer readable storage medium such as computer readable memory ROM, random access memory RAM, magnetic or optical disk, etc.

The embodiment of the application further provides a chip, the chip comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running a program or instructions, each process of the session channel establishment method embodiment of the non-3 GPP device can be realized, the same technical effect can be achieved, and the repetition is avoided, and the description is omitted here.

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

The embodiments of the present application further provide a computer program/program product, where the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement each process of the session channel establishment method embodiment of the non-3 GPP device, and the same technical effects can be achieved, so that repetition is avoided, and details are not repeated here.

The embodiment of the application also provides a communication system, which comprises: the terminal device and the network side device, wherein the terminal device can be used for executing the steps of the session channel establishment method of the non-3 GPP device, and the network side device can be used for executing the steps of the session channel establishment method of the non-3 GPP device.

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

From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a computer software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present application.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are to be protected by the present application.

Claims

1. A method for establishing a session channel of a non-3 GPP device, comprising:

the terminal equipment acquires a session policy of the non-3 GPP equipment;

2. The method of claim 1, wherein the session policy of the non-3 GPP device comprises at least one of:

3. The method of claim 2, wherein the session policy of the non-3 GPP device further comprises at least one of:

identification information of one or more non-3 GPP devices using one QoS flow;

establishment parameters of session channels.

4. A method according to claim 3, wherein the session channel establishment parameters comprise at least one of:

An IP type;

an Ethernet type;

a business continuity mode;

a control surface channel;

a user plane channel;

a data network name DNN of the session channel;

network slice identification of the session channel.

5. The method according to claim 1, wherein the terminal device obtains a session policy of a non-3 GPP device, comprising:

or alternatively, the process may be performed,

6. The method according to claim 1, wherein the terminal device requests a core network device to establish a session channel for the non-3 GPP device according to a session policy of the non-3 GPP device, the method further comprising:

the terminal equipment acquires the identification information of the non-3 GPP equipment;

the terminal equipment requests the core network equipment to establish a session channel for the non-3 GPP equipment according to the session policy of the non-3 GPP equipment, and the method comprises the following steps:

7. The method according to claim 6, wherein the terminal device requests a core network device to establish a session channel for the non-3 GPP device according to a session policy of the non-3 GPP device and identification information of the non-3 GPP device, comprising:

8. The method of claim 7, wherein the first PDU session establishment request message or the first PDU session modification request message comprises at least one of:

identification information of the non-3 GPP device,

9. The method according to claim 7 or 8, wherein the first PDU session establishment response message or the first PDU session modification response message comprises: a second non-3 GPP access indication for indicating a successful establishment of a PDU session or QoS flow for the non-3 GPP device.

10. The method of claim 5, wherein the terminal device obtains the session policy of the non-3 GPP device from a core network device, comprising:

or alternatively, the process may be performed,

11. The method according to claim 10, wherein the terminal device obtains the session policy of the non-3 GPP device in a PDU session establishment procedure or a PDU session modification procedure of the terminal device, comprising:

The terminal equipment sends a second PDU (protocol data unit) session establishment request message or a second PDU session modification request message to the core network equipment, wherein the second PDU session establishment request message is used for requesting to establish the PDU session of the terminal equipment, and the second PDU session modification request message is used for requesting to modify the PDU session of the terminal equipment;

the terminal equipment receives a second PDU session establishment response message or a second PDU session modification response message sent by the core network equipment; the second PDU session establishment response message is used for indicating the PDU session of the terminal equipment to be successfully established; the second PDU session modification response message is used for indicating successful PDU session modification of the terminal equipment;

12. The method of claim 11, wherein the second PDU session establishment request message or the second PDU session modification request message comprises at least one of:

identification information of the terminal device.

13. The method according to claim 10, wherein the terminal device obtains the session policy of the non-3 GPP device during the registration of the terminal device, comprising:

14. The method of claim 13, wherein the registration request message comprises at least one of:

identification information of the terminal device.

15. The method according to any of claims 1-14, wherein the identification information of the non-3 GPP device comprises at least one of:

an equipment identity of the non-3 GPP equipment;

a connection identifier of the non-3 GPP device;

and the type identification of the non-3 GPP equipment.

16. The method of claim 15, wherein the device identification of the non-3 GPP device comprises at least one of:

A MAC address of the non-3 GPP device;

an international mobile subscriber identity IMSI of the non-3 GPP device;

a user permanent identifier, SUPI, of the non-3 GPP device;

a user temporary identifier, sui, of the non-3 GPP device;

the general public user identity GPSI of the non-3 GPP device.

17. The method of claim 15, wherein the connection identification of the non-3 GPP device comprises at least one of:

18. The method of claim 15, wherein the type identification of the non-3 GPP device comprises at least one of:

service identification required by the non-3 GPP equipment;

service requirement information of the non-3 GPP equipment;

and the identification of the group to which the non-3 GPP device belongs.

19. A method for establishing a session channel of a non-3 GPP device, comprising:

20. The method of claim 19, wherein the session policy of the non-3 GPP device comprises at least one of:

21. The method of claim 20, wherein the session policy of the non-3 GPP device further comprises at least one of:

identification information of one or more non-3 GPP devices using one QoS flow;

establishment parameters of session channels.

22. The method of claim 21, wherein the session channel establishment parameters include at least one of:

an IP type;

an Ethernet type;

a business continuity mode;

a control surface channel;

a user plane channel;

a data network name DNN of the session channel;

network slice identification of the session channel.

23. The method of claim 19, wherein the core network device obtains a session policy of a non-3 GPP device, comprising:

Or alternatively, the process may be performed,

24. The method of claim 19, wherein the method further comprises:

25. The method of claim 24, wherein the core network device sending the session policy of the non-3 GPP device to a terminal device comprises:

or alternatively, the process may be performed,

26. The method according to claim 25, wherein the core network device sending the session policy of the non-3 GPP device to the terminal device in a PDU session establishment procedure or a PDU session modification procedure of the terminal device, comprising:

27. The method of claim 26, wherein the second PDU session establishment request message or the second PDU session modification request message comprises at least one of:

identification information of the terminal device.

28. The method according to claim 25, wherein the core network device sending the session policy of the non-3 GPP device to the terminal device during the registration of the terminal device, comprises:

29. The method of claim 28, wherein the registration request message comprises at least one of:

identification information of the terminal device.

30. The method according to claim 19, wherein the core network device establishes a session channel for the non-3 GPP device according to the session policy of the non-3 GPP device and the request of the terminal device, comprising:

31. The method of claim 30, wherein the first PDU session establishment request message or the first PDU session modification request message comprises at least one of:

identification information of the non-3 GPP device,

32. The method according to claim 30 or 31, wherein the first PDU session establishment response message or the first PDU session modification response message comprises: a second non-3 GPP access indication for indicating a successful establishment of a PDU session or QoS flow for the non-3 GPP device.

33. A session channel establishment apparatus for a non-3 GPP device, comprising:

34. A terminal device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the session channel establishment method of a non-3 GPP device according to any one of claims 1 to 18.

35. A session channel establishment apparatus for a non-3 GPP device, comprising:

36. A network side device comprising a processor and a memory storing a program or instructions executable on the processor, which when executed by the processor, implement the steps of the session channel establishment method of a non-3 GPP device according to any of claims 19 to 32.

37. A readable storage medium, wherein a program or instructions is stored on the readable storage medium, which when executed by a processor, implements the session channel establishment method of a non-3 GPP device according to any one of claims 1 to 18, or the steps of the session channel establishment method of a non-3 GPP device according to any one of claims 19 to 32.