RU2776678C2 - Method and device for session processing - Google Patents

Abstract

FIELD: mobile communication.

SUBSTANCE: claim relates to the field of mobile communication technology and, in particular, to a method and a device for session processing. The method for session processing contains stages, at which an application (hereinafter – APP) is initiated using a terminal device, a session type corresponding to APP is determined based on UE route selection policy (URSP), and the first message is transmitted to an object of access and mobility control function (hereinafter – AMF), wherein the first message includes the session type, and it is used for a request for establishing the session of the specified type. In the method, when the first message used for a request for establishing PDU session is initiated in AMF object, the terminal device adds PDU session type to the first message in such a way that a network side can establish PDU session of the corresponding type based on PDU session type, which is sent by the terminal device.

EFFECT: increase in correctness of communication between a terminal device and a network side.

26 cl, 4 dwg, 2 tbl

Description

The field of technology to which the invention belongs

The present application relates to the field of mobile communication technologies and, in particular, to a session processing method and apparatus.

State of the art

In 5th generation (5G) mobile communications, many types of packet data unit (PDU) sessions are defined, such as an Internet type session, an Ethernet type session, and an unstructured type session.

When there are multiple types of PDU sessions, the problem to be solved is how to set up the correct PDU session type for the terminal.

Disclosure of the essence of the invention

The present application provides a session processing method and apparatus for establishing a session PDU of the correct type for a terminal device.

To solve the above problem, the present application provides the following technical solutions:

According to a first aspect, the present application provides a method for handling a session, including: initiating, by a terminal, APPs and determining a session type of a Packet Data Unit (PDU) based on the APP; and sending, by the terminal, a first message to an Access and Mobility Management Function (AMF) entity, where the first message includes the session type, and the first message is used to request the establishment of the PDU session type. In the method, when initiating, in the AMF entity, the first message used to request the establishment of a PDU session, the end device adds the session type of the PDU to the first message so that the network side can establish a PDU session of the appropriate type based on the session type of the PDU that is transmitted by the end device. to establish a session PDU of the correct type for the terminal device, thereby improving the correctness of communication between the terminal device and the network side.

In an exemplary embodiment, the determination, by the end device, of the session type of the PDU includes: determining, by the end device, based on the first match, the session type corresponding to the APP, where the first match is the match between the APP and the session type of the PDU. In the method, the terminal device determines the session type of the PDU based on the mapping between the APP and the session type of the PDU. It's easy to implement.

Optionally, the first match is preconfigured in the terminal, or the first match is obtained by the terminal from the AMF entity.

In an exemplary embodiment, determining, by the end device, the PDU session type includes: determining, by the end device, based on the second match of the DN corresponding to the APP; determining, by the end device, the DN type corresponding to the DN identifier; and determining, by the terminal based on the third match, a session type corresponding to the DN type, where the second match is a match between the APP and the DN ID, and the third match is a match between the DN type and the session type of the PDU.

In an exemplary embodiment, the terminal sends a request message to the AMF entity and receives the DN and DN type that are sent by the AMF entity based on the request message; or, the terminal device receives the DN identifier and the DN type, which are transmitted by the radio access network (RAN) device.

In an exemplary embodiment, the terminal transmits the first DN information to the AMF entity, where the first DN information includes the DN identifier or includes the DN identifier and the DN type, the first DN information is used by the AMF entity to determine the SMF entity based on the DN identifier, and the entity The SMF is configured to establish the session type of the PDU.

According to a second aspect, the present application provides a session processing method including: receiving, by a session management function (SMF) entity, a second message from an access and mobility management function (AMF) entity, where the second message includes a session type, a packet data unit session (PDU) requested by the end device, and the second message is used to request the establishment of a PDU session; and establishing, by the SMF entity, a session PDU based on the session type of the PDU.

Optionally, the SMF entity receives the DN from the AMF entity; and

the SMF object defines a user plane function (UPF) object based on the DN and the PDU session type, where the UPF object is configured to set the PDU session type.

According to a third aspect, the present application provides a session processing method including: receiving, by a session management function (SMF) entity, a second message from an access and mobility management function (AMF) entity, where the second message includes second data network (DN) information ), and the second message is used to request the establishment of a PDU session; and determining, by the SMF entity, the PDU session type based on the second DN information.

Optionally, when the second DN information includes the DN identifier, determining, by the SMF entity, a PDU session type based on the second DN information includes: determining, by the SMF entity, a DN type based on the DN identifier, and determining a PDU session type based on the type DN; or

when the second DN information includes the DN type, determining, by the SMF entity, a PDU session type based on the second DN information includes: determining, by the SMF entity, a PDU session type based on the DN type.

Optionally, if the second message carries the session type of the session PDU requested by the end device, when the session type of the PDU that is determined by the SMF based on the second DN information does not match the session type of the session PDU requested by the end device, the method further includes:

sending, by the SMF entity, a session reject message to the terminal, where the session reject message includes a session type PDU that is determined by the SMF entity based on the second DN information.

Optionally, the SMF entity establishes a PDU session based on the session type.

In an exemplary embodiment, the SMF entity determines a user plane function (UPF) entity based on the second DN information and establishes a session PDU of the session type.

According to a fourth aspect, the present application provides a session processing method including: receiving, by an AMF entity, a first message and first data network DN information from a terminal device, where the first message is used to request a session establishment of a PDU and determining, by an AMF entity , a session management function (SMF) object based on the first DN information; and transmitting, by the AMF entity, a second message to the SMF entity based on the first message, where the second message is used to request the establishment of a PDU session and the session type of the PDU corresponds to the first DN information.

Optionally, the first message and the second message include the session type, session PDU, requested by the terminal; or the first DN information includes a DN identifier, the second message includes a DN identifier, and the DN identifier is used by the SMF entity to determine the PDU session type based on the DN identifier.

Optionally, the first DN information includes a DN identifier; and

determining, by the AMF entity, a session management function (SMF) entity based on the first DN information includes:

determining, by the AMF object, the DN type based on the DN identifier;

transferring, by the AMF entity, the DN identifier and the DN type to the NRF entity; and

receiving, by the AMF entity, the SMF entity from the NRF entity, where the SMF entity is determined by the NRF entity based on the DN identifier and the DN type.

Optionally, the AMF entity receives a registration request message from the terminal;

the AMF entity obtains, from the database, based on the registration request message, DN information subscribed by the terminal device, where the subscribed DN information includes a DN identifier and a DN type; and

the AMF object conveys to the end device the DN information to which the end device is subscribed.

In an exemplary embodiment, the registration request message includes tag capability indication information, where the capability indication information is used to indicate a data network supported by the tag; and

the DN information subscribed to by the end device corresponds to the data network supported by the end device.

According to a fifth aspect, the present application provides a device. The device may be a terminal device or a chip in a terminal device. The device has the functions of implementing various embodiments of the first aspect. The functions may be implemented in hardware, or may be implemented in hardware running corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, when the device is a terminal device, the terminal device includes a processing unit and a communication unit. The processing unit may be, for example, a processor. The communication unit may be, for example, a transceiver, and the transceiver includes RF circuitry. If necessary, the terminal device further includes a storage unit, and the storage unit may be, for example, a memory. When the terminal device includes a storage unit, the storage unit is configured to store computer-executable instructions. The processing unit is connected to the storage unit. The processing unit executes computer-executable instructions stored in the storage unit for executing the session processing method in any embodiment of the first aspect to the end device.

In another possible embodiment, when the device is a chip in a terminal device, the chip includes a processing unit and a communication unit. The processing unit may be, for example, a processor. The communication unit may be, for example, an input/output interface, a pin, or a circuit. The processing unit may execute computer-executable instructions stored in the storage unit to enable execution of the session processing method in any embodiment of the first aspect. Optionally, the storage unit is a storage unit located on the chip, such as a register or buffer, or the storage unit may be a storage unit located on the target device but outside the chip, such as read-only memory (ROM), another type of static storage device capable of storing static information and instructions, or random access memory (RAM).

A processor referred to anywhere above may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of a method program. session processing in the first aspect.

According to the sixth aspect, the present application provides a device. The device may be an SMF object, or it may be a chip in an SMF object. The device has the functions of implementing various embodiments of the second aspect. The functions may be implemented in hardware, or may be implemented in hardware running corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, when the device is an SMF entity, the SMF entity includes a processing unit and a communication unit. The processing unit may be, for example, a processor. The communication unit may be, for example, a transceiver, and the transceiver includes RF circuitry. Optionally, the SMF object further includes a storage unit, and the storage unit may be a memory, for example. When the SMF object includes a storage unit, the storage unit is configured to store a computer-executable instruction. The processing unit is connected to the storage unit. The processing unit executes a computer-executable instruction stored in the storage unit to enable the SMF object to execute the session processing method in any embodiment of the second aspect.

In another possible embodiment, when the device is a chip in an SMF entity, the chip includes a processing unit and a communication unit. The processing unit may be, for example, a processor. The communication unit may be, for example, an input/output interface, a pin, or a circuit. The processing unit may execute a computer-executable instruction stored in the storage unit to enable execution of the session processing method in any embodiment of the second aspect. Optionally, the storage unit is a storage unit located on the chip, such as a register or buffer, or the storage unit may be a storage unit located in the SMF object but outside the chip, such as a ROM, another type of static storage device that can store static information and instructions, or RAM.

The processor mentioned anywhere above may be a general purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling program execution of the session processing method in the first aspect.

According to the seventh aspect, the present application provides a device. The device may be an SMF object, or it may be a chip in an SMF object. The device has the functions of implementing various embodiments of the third aspect. The functions may be implemented in hardware, or may be implemented in hardware running corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, when the device is an SMF entity, the SMF entity includes a processing unit and a communication unit. The processing unit may be, for example, a processor. The communication unit may be, for example, a transceiver, and the transceiver includes RF circuitry. Optionally, the SMF object further includes a storage unit, and the storage unit may be a memory, for example. When the SMF object includes a storage unit, the storage unit is configured to store a computer-executable instruction. The processing unit is connected to the storage unit. The processing unit executes a computer-executable instruction stored in the storage unit to enable the SMF object to execute the session processing method in any embodiment of the third aspect.

In another possible embodiment, when the device is a chip in an SMF entity, the chip includes a processing unit and a communication unit. The processing unit may be, for example, a processor. The communication unit may be, for example, an input/output interface, a pin, or a circuit. The processing unit may execute a computer-executable instruction stored in the storage unit to enable execution of the session processing method in any embodiment of the third aspect. Optionally, the storage unit is a storage unit located on the chip, such as a register or buffer, or the storage unit may be a storage unit located in the SMF object but outside the chip, such as a ROM, another type of static storage device capable of storing static information and instructions, or RAM.

The processor mentioned anywhere above may be a general purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling program execution of the session processing method in the first aspect.

According to the eighth aspect, the present application provides a device. The device may be an AMF object, or it may be a chip in an AMF object. The device has the functions of implementing various embodiments of the fourth aspect. The functions may be implemented in hardware, or may be implemented in hardware running corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

Optionally, when the device is an AMF entity, the AMF entity includes a processing unit and a communication unit. The processing unit may be, for example, a processor. The communication unit may be, for example, a transceiver, and the transceiver includes RF circuitry. Optionally, the AMF object further includes a storage unit, and the storage unit may be a memory, for example. When the AMF object includes a storage unit, the storage unit is configured to store a computer-executable instruction. The processing unit is connected to the storage unit. The processing unit executes a computer-executable instruction stored in the storage unit to enable the AMF object to execute the session processing method in any embodiment of the fourth aspect.

In another possible embodiment, when the device is a chip in an AMF entity, the chip includes a processing unit and a communication unit. The processing unit may be, for example, a processor. The communication unit may be, for example, an input/output interface, a pin, or a circuit. The processing unit may execute a computer-executable instruction stored in the storage unit to enable execution of the session processing method in any embodiment of the fourth aspect. Optionally, the storage unit is a storage unit located on the chip, such as a register or buffer, or the storage unit may be a storage unit located in the AMF object but outside the chip, such as a ROM, another type of static storage device capable of storing static information and instructions, or RAM.

The processor mentioned anywhere above may be a general purpose central processing unit (CPU), a microprocessor, an ASIC, or one or more integrated circuits for controlling the execution of the session processing method program in the fourth aspect.

According to a ninth aspect, the present application further provides for a computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method in the first aspect. The computer may be, for example, a terminal device.

According to a tenth aspect, the present application further provides for a computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method in the second aspect. The computer may be, for example, an SMF object.

According to an eleventh aspect, the present application further provides for a computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to execute the method in the third aspect. The computer may be, for example, an SMF object.

According to a twelfth aspect, the present application further provides for a computer-readable storage medium. The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to execute the method in the fourth aspect. The computer may be, for example, an AMF object.

According to a thirteenth aspect, the present application provides a computer program product. The computer program product includes computer software instructions, where the computer software instructions can be loaded by a processor to implement a procedure of the session processing method in any embodiment of the first aspect.

According to a fourteenth aspect, the present application provides a computer program product. The computer program product includes computer software instructions, and the computer software instructions may be loaded by a processor to implement a procedure of the session processing method in any embodiment of the second aspect.

According to a fifteenth aspect, the present application provides a computer program product. The computer program product includes computer software instructions, and the computer software instructions may be loaded by a processor to implement a procedure of the session processing method in any embodiment of the third aspect.

According to the sixteenth aspect, the present application provides a computer program product. The computer program product includes computer software instructions, and the computer software instructions can be downloaded by a processor to implement the procedure of the session processing method in any embodiment of the fourth aspect.

In addition, in order to explain the technical effects obtained in accordance with any of the embodiments of the second aspect to the sixteenth aspect, reference should be made to the technical effects obtained in accordance with the various embodiments of the first aspect. In this document, their details are not re-described.

These or other aspects of the present invention will be more clear and understandable from the descriptions of the following embodiments.

Brief description of the drawings

Figure 1 shows a simplified diagram of a possible network architecture to which the present application applies;

Figure 2 shows a flowchart of the session processing method according to the present application;

Figure 3 shows a flowchart of another session processing method according to the present application; and

Figure 4 shows a simplified diagram of the device according to the present application.

Implementation of the invention

In order to explain the objectives, technical solutions and advantages of the present application, the present application is described in detail below with reference to the accompanying drawings.

It should be noted that the session processing method of the present application may be performed by a device. On the network side, the device can be a Session Management Function (SMF) object or chip in an SMF object, or a device can be an Access and Mobility Management Function (AMF) object or chip in an AMF object. On the tag side, the device can be a tag or a chip in a tag.

To simplify the description in this application, the session processing method is described using an example in which the device is an AMF entity, an SMF entity, or a terminal device. For an implementation method in which the device is a chip in an AMF object, a chip in an SMF object, or a chip located in a terminal device, see the specific description of the session processing method in which the device is an AMF object, an SMF object, or a terminal device. This document does not re-describe the details.

Figure 1 shows a simplified diagram of a possible network architecture to which the present application applies. A simplified network architecture diagram includes a terminal, a 3rd Generation Partnership Project (3GPP) network entity, a non-3GPP access network (Non-3GPP), an N3IWF, an AMF entity, a session management function entity, SMF), user plane function object (UPF), data network (data Network, DN), etc.

The terminal device is a device with wireless reception and transmission functions. The terminal may be deployed on land, such as an indoor or outdoor device, a handheld device, or a vehicle, or may be deployed on the surface of the water (such as a ship) or may be deployed in the air (such as an aircraft, a hot air balloon). or satellite). The terminal device may be a mobile phone (mobile phone), a tablet computer (pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control system, wireless terminal in self driving system, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in system transport safety, a wireless terminal in a smart city system, a wireless terminal in a smart home system, etc.

The 3GPP access network entity is also referred to as a radio access network (RAN) entity and may be, for example, a base station in 5G. A non-3GPP access network is an access network that is different from a 3GPP access network, such as a wireless local area networks (WLAN) access network. The N3IWF is similar to an evolved packet data gateway (ePDG) in long term evolution (LTE), and is configured to: when a UE accesses a 5G network using non-3GPP technology, establish an Internet Protocol Security Tunnel ( internet protocol security, IPsec) with the UE. In the future definition of 5G, the name "N3IWF" may be changed.

The AMF entity is responsible for organizing access and managing the mobility of the end device. In a real application, an AMF entity includes a mobility management function in a mobility management entity (MME) in a long term evolution (LTE) network infrastructure, and an access control function is added to the AMF entity.

The SMF object is responsible for session management, that is, the session management function in the MME object, such as establishing a session for a user. The UPF object is the user plane functional entity of the end device and is primarily responsible for connecting to the external network. The UPF entity provides the related functions of the serving gateway (SGW) and gateway (gateway) of the public data network (PDN) LTE. The DN is responsible for providing the data service for the end device, such as providing the network access function and the text messaging function for the end device.

In the present application, the DN is used to identify the data network. A new DN attribute type has been added. Type (Type) DN is used to indicate the type of data network. For example, the DN type includes the Internet (internet), Ethernet (Ethernet) and unstructured (unstructured) network.

In the present application, the DN identifier and/or DN type may be collectively referred to as DN information. More specifically, the DN information includes a DN identifier, or the DN information includes a DN type, or the DN information includes a DN identifier and a DN type.

In the implementation, in the 3GPP standard, the currently defined data network name (DNN) is used to identify the data network, and according to the currently defined name "DNN", DNN is only used as a transmission network identifier. data, i.e. as a DN identifier. In the present application, after adding a new DN type, there are two following implementations of the DN type indication.

In a first implementation, the DN identifier and DN type may be specified separately using independent information elements. More specifically, the DN identifier is still identified using the DNN defined in the current 3GPP standard, and a new Type DN information element is independently defined to identify the DN type.

In a second implementation, the DN identifier and the DN type may be indicated by the same information element. For example, the definition of a current DNN is extended so that a DNN can specify both a DN identifier and a DN type. Specifically, a field, that is, a DN type, is added to the current DNN. In other words, an extended DNN includes a DN identifier and a DN type. In one example, a DNN field may be defined in two parts. The value of the previous part of the field is used to identify the DN identifier. For example, 0001 identifies the company's internal network. The value of the last part of the field is used to identify the DN type. For example, 0002 identifies that the internal enterprise network is of type Ethernet. In this case, the entire 00010002 field is a specific DNN value. In an implementation, this DNN information element includes two pieces of information: a DN identifier and a DN type.

According to the above two implementations, it can be understood that the DN referred to in the following embodiments refers to a DNN (first implementation) or a field that resides in a DNN and is used to identify a data network (second implementation).

Based on the system architecture shown in FIG. 1, the present application provides a session processing method including: initiating, by a terminal, APPs and determining a session type of a Packet Data Unit (PDU) based on the APP; and sending, by the terminal, a first message to an Access and Mobility Management Function (AMF) entity, where the first message includes the session type, and the first message is used to request the establishment of the session type of the PDU. In the method, when initiating, in the AMF entity, the first message used to request the establishment of a session PDU, the end device adds the session type of the PDU to the first message so that the network side can establish a PDU session of the appropriate type based on the session type of the PDU that is sent by the end device. device to establish a session of the correct type of PDU for the terminal device, thereby improving the correctness of communication between the terminal device and the network side.

The following describes in more detail the session processing method presented in the present application with reference to the accompanying drawings.

Embodiment 1

In Embodiment 1, the terminal may determine the session type of the PDU and send the session type to the network side to establish the PDU session.

Figure 2 shows a flowchart of the session processing method according to the present application. The method includes the following steps.

Step 201: The tag initiates the APP and determines the PDU session type based on the APP.

An application (APP) may be a specific application such as "Youku" or "Baidu", or may be an application type such as a video application, a text application, or an image application.

When determining application initiation (APP), the terminal may determine the PDU session type based on the APP. The following are two implementations as examples for description.

Implementation 1: Based on the first match, the terminal determines the PDU session type that matches the APP.

The first match records the match between the APP and the PDU session type that matches the APP.

The first match may be written as a table, or may be written as an array, or may be written as a function. The present application is not limited to this.

For example, in a particular implementation, the first match may be implemented in conjunction with a prior art UE Route Selection Policies (URSP) policy table. Table 1 is a prior art URSP table.

Table 1

Data matching rule (Traffic filter) App=DummyApp (video app) Data upload policy (Direct offload) Forbidden Slice Info S-NSSAI-a Session Continuity Types Mode 3 SSC DN ID Internet Access Type 3GPP Access

The traffic filter is related to the data mapping rule, and this setting is used to determine, based on the APP initiated by the end device, whether the following other policies apply. For example, in Table 1, when the end device initiates the Youku application, since Youku is a video application, this policy determines that the other policies in the table apply to the Youku application. When the end device launches the WeChat application, the other policies in the table are not applied.

Direct upload refers to the data upload policy, and this setting is used to determine which APP or APP type can use data upload. For example, in Table 1 above, "Forbidden" means that the video application cannot use data upload.

The slice information is slice information, and this parameter is used to define slice information to be used to initiate an APP so that the UE adds slice information when initiating a PDU session. For example, in Table 1 above, when initiating APP, the UE determines that slice information S-NSSAI-a needs to be used.

Continuity Types represent the type of session continuity and this parameter is used to determine the type of session continuity requested by the APP. For example, in Table 1 above, when initiating APP, the UE determines that slice information S-NSSAI-a needs to be used.

The DN identifier is the identifier of the data network and this parameter is used to specify the name of the data network. For example, in Table 1 above, the data network indicated by the DN is the Internet.

Access Type is the type of access and this parameter is used to determine the type of access requested by the application. For example, in Table 1 above, when initiating the APP, the UE determines that the required access type is the 3GPP access type.

Based on Table 1, if it is necessary to record a correspondence between DummyApp and a PDU session type that corresponds to APP, the "PDU Type" attribute can be added to the above Table 1. "PDU Type" is a PDU session type, so the first correspondence is established. Table 2 is a URSP table to which the PDU Type attribute has been added.

table 2

Data matching rule (Traffic filter) App=DummyApp (video app) Data upload policy (Direct offload) Forbidden Slice Info S-NSSAI-a Session Continuity Types Mode 3 SSC DN ID Internet Access Type 3GPP Access Packet Data Unit (PDU Type) Session Type ethernet

Thus, when initiating the DummyApp application, the terminal can determine, in particular, according to the first correspondence in the previous table 2, the correspondence between DummyApp and PDU type, that the PDU type corresponding to DummyApp is Ethernet.

The first mapping may be pre-configured in the terminal device or may be obtained by the terminal device from the network side, for example from the AMF entity.

The implementation of Table 2 above is used as an example. The above URSP table may be pre-configured in the terminal device. Alternatively, when moving to a data network coverage area, the terminal device may receive the URSP table broadcast by the data network, and the terminal device may locally store the received URSP table or update the locally stored URSP table based on the received URSP table.

Implementation 2: End device determines PDU session type based on APP, DN ID and DN type.

Thus, the terminal can first obtain the DN information from the network side, such as an AMF entity, where the DN information includes the DN ID and the DN type. The method of obtaining includes, but is not limited to:

Receive Method 1: The end device sends a request message to the AMF entity to request to obtain the DN ID and DN type.

For example, when transitioning to a data network, the terminal may send a registration request message to the AMF entity. After receiving the registration request message, the AMF entity obtains, from the database, the DN information to which the terminal is subscribed, where the DN information includes the DN identifier and the DN type. The AMF object then sends the DN ID and DN type to the end device so that the end device gets the DN ID and DN type.

Optionally, the registration request message includes the capability indication information of the terminal device, where the capability indication information is used to indicate the communication network supported by the terminal device. In this case, the signed DN information sent by the AMF entity to the terminal device is the DN information corresponding to the data communication network supported by the terminal device. For example, if the capability indication information indicates that the communication network supported by the terminal device is the Internet, the signed DN information sent by the AMF entity to the terminal device includes a DN identifier and a DN type that are related to the Internet, rather than an identifier DN and DN type that refer to another data network.

If necessary, the AMF entity sends the DN information or DN identifier to the PCF entity. If necessary, the PCF entity determines the DN service range based on the DN information or the DN identifier, and sends the service range information to the AMF entity.

If necessary, the AMF entity determines, based on information about the current location of the tag, whether the tag is currently within the service range of the DN. If the end device is currently within the service range of the DN, the AMF entity decides to send the DN information to the end device. For example, the AMF sends a response message to the terminal device, where the response message includes DN information, and the DN information includes a DN identifier and a DN type.

If necessary, the AMF entity notifies the end device of the DN service range, and the end device determines whether the end device is currently in the DN service range.

Acquisition Method 2: The terminal obtains the DN and the DN type, which are transmitted by a RAN device such as a base station.

Assuming that the tag can obtain the DN and the DN type from the network side, when initiating the APP, the tag first determines, based on the second match, the DN corresponding to the APP. The second match is the match between APP and DN. For example, the second match may be recorded in the previous table 1. The DN corresponding to the APP may be obtained based on the APP. In addition, the DN ID is the DN ID received by the end device from the network side.

The end device then determines the DN type corresponding to the DN identifier. The DN type is the DN type received by the end device from the network side.

The terminal device then determines, based on the third match, the PDU session type that matches the DN type. The third match is the match between DN type and PDU session type. The third mapping may be pre-configured in the terminal device.

In implementation 2, the mapping between APP and DN and the mapping between DN type and PDU session type are pre-configured in the terminal device. Thus, after receiving the DN ID and DN type from the network side, the terminal device can determine the DN based on the triggered APP, determine the DN type based on the DN ID, and determine the PDU session type based on the DN type.

Step 202: The tag sends a first message to the AMF entity and the AMF entity receives the first message from the tag.

The first message includes the session type of the PDU, and the first message is used to request the establishment of the session type of the PDU.

In this embodiment, when sending the first message used to request the establishment of a session PDU to the AMF entity, the end device adds the session type of the PDU to the first message so that the network side can establish a PDU session of the appropriate type based on the session type of the PDU sent by the end device. in order to establish a session PDU of the correct type for the terminal device, thereby ensuring correct communication between the terminal device and the network side.

If necessary, after the above step 202, the method further includes the following steps.

Step 203: The terminal sends the first DN information to the AMF entity, and the AMF entity receives the first DN information from the terminal. The first DN information includes a DN identifier, or the first DN information includes a DN identifier and a DN type (the specific form of the first DN information may be any of the above two implementations).

It should be noted that step 203 may alternatively be performed before step 202. Alternatively, step 202 and step 203 may be combined into one step. In other words, the terminal simultaneously transmits the first message and the first DN information to the AMF entity, for example, transmits the first message and the first DN information using the NAS message.

Step 204: The AMF entity determines the SMF entity based on the first DN information.

When the first DN information includes a DN identifier, the AMF entity must also determine the type of the DN based on the DN identifier. In addition, the AMF object selects the SMF object based on the DN ID and the DN type.

When the first DN information includes the DN ID and the DN type, the AMF object selects the SMF object based on the DN ID and the DN type.

For example, the AMF object sends the DN and DN type to the Network Function Repository Function (NRF) object, and the NRF object selects the SMF object based on the received DN and DN type and sends the SMF object to the AMF object in order to the AMF object could determine the SMF object to be used.

Step 205: The AMF entity sends the second message to the SMF entity.

The second message is derived from the first message. In particular, after receiving the first message, the AMF object does not receive the content of the first message, but generates a second message based on the first message and passes the second message to the SMF object. That is, the second message includes the first message.

Optionally, at step 205, the second message further includes second DN information. The second DN information includes a DN identifier, or the second DN information includes a DN identifier and a DN type (the specific form of the second DN information may be any of the above two implementations).

If the second DN information passed by the AMF entity to the SMF entity includes a DN identifier, the SMF entity further determines the DN type based on the DN identifier. In addition, the SMF entity may determine the PDU session type based on the DN type.

If the second DN information passed by the AMF entity to the SMF entity includes a DN identifier and a DN type, the SMF entity may determine the PDU session type based on the DN type.

If necessary, the SMF entity compares the session type of the PDU that is obtained from the second message with the session type of the PDU that is determined by the SMF entity. If the two session types are the same, the SMF entity executes step 206; or, if the two session types are different, the SMF entity executes step 207.

Step 206: The SMF entity establishes a PDU session based on the second message.

Specifically, the SMF entity establishes a session PDU based on the session type of the PDU that is obtained from the second message. Specifically, the SMF entity receives the session type of the PDU that is carried in the first message in the second message.

Since the PDU session type that the SMF entity obtains from the second message is the same as the PDU session type that is determined by the SMF entity, the SMF entity can directly establish a PDU session based on the PDU session type that is in the second message.

This completes the procedure.

From step 201 to step 206, the tag adds the PDU session type to the first message when sending the first message to the AMF entity, and then the AMF entity sends the PDU session type to the SMF entity using the second message, so the SMF entity establishes the PDU session based on the session type. Thus, a PDU session of the correct type is established.

Step 207: The SMF entity sends a session reject message to the terminal using the AMF entity.

If the session type of the PDU that is received by the SMF entity from the second message is different from the session type of the PDU that is specified by the SMF entity, the SMF entity sends a session reject message to the end device. Optionally, the session reject message includes a PDU session type that is determined by the SMF based on the DN information.

More specifically, the SMF entity considers that the session type of the PDU that is carried in the first message sent by the terminal in the previous step 202 is incorrect, and further considers that another parameter associated with the first message is also incorrect. Thus, the SMF entity sends a session reject message to the terminal device, where the session reject message carries the PDU session type, which is determined by the SMF entity, so that the terminal device re-initiates the PDU session request process, adds the correct session PDU type to to the new request and adds another valid parameter to the new request, where the valid session type PDU is the session type that is sent by the SMF entity to the terminal using the session reject message.

Step 208: The tag sends a third message to the AMF entity and the AMF entity receives the third message from the tag.

This step is similar to step 202. However, the third message in step 208 carries the session PDU type that the SMF adds to the session reject message, ie the correct session PDU type. The third message is used to request the establishment of a PDU session.

Step 209: The AMF entity sends a fourth message to the SMF entity and the SMF entity receives the fourth message from the AMF entity.

This step is similar to step 205. However, the fourth message in step 209 is generated based on the third message, and the AMF entity does not know the content of the third message and the content of the fourth message. The fourth message carries the correct session type PDU. The fourth message is used to request the establishment of a PDU session.

Step 210: The SMF entity establishes a PDU session based on the fourth message.

This completes the procedure.

In steps 201-205 and steps 207-210, the terminal adds the session type PDU to the first message when sending the first message to the AMF entity, then the AMF entity sends the session type PDU with the SMF entity using the second message, upon determining that the received session type The PDU is invalid, the SMF entity instructs the terminal to re-initiate the third message, and the SMF entity receives the fourth message from the AMF entity to obtain the correct session type with the fourth message and establish the session PDU. Thus, the correct PDU session type is established.

Optionally, after step 205, the SMF entity may alternatively establish a PDU session directly. In other words, the SMF entity directly establishes, based on the type of session PDU that is in the second message, the session PDU corresponding to the session type. In particular, the SMF entity does not determine whether the session type of the PDU that is determined by the SMF entity is the same as the session type of the PDU that is carried in the second message.

Optionally, in step 206 or step 210, when establishing a PDU session, the SMF entity establishes a PDU session along with the UPF entity. So the SMF object must also select the UPF object. Optionally, the SMF entity determines the UPF entity based on the DN and the session type of the PDU where the DN may be sent, by the AMF entity, to the SMF entity.

Embodiment 2

The main difference between this embodiment and Embodiment 1 is that the terminal device does not send the PDU session type to the network side, but the SMF entity on the network side determines the PDU session type and establishes the PDU session.

Figure 3 shows a flowchart of another session processing method according to the present application. The method includes the following steps.

Step 301: The tag initiates the APP and determines the DN.

At the stage when the APP is initiated, the end device cannot obtain the session type of the PDU, but can determine the DN corresponding to the APP. In other words, the terminal may determine the identifier of the data network to which the terminal is to access.

For example, in an implementation, a terminal may obtain, according to Table 1 in the previous Embodiment 1, a DN corresponding to an APP.

Step 301 may be implemented according to the prior art, and the details will not be repeated here.

Step 302: The terminal sends the first message and the first DN information to the AMF entity.

The first DN information includes a DN identifier. The first message is used to request the establishment of a PDU session, and the first DN information may be used by the AMF entity to determine the SMF entity.

If necessary, the method further includes the following steps.

Step 303: The AMF entity determines the SMF entity based on the first DN information.

Step 303 is similar to step 204 presented in Embodiment 1. More specifically, the AMF entity first determines the DN type based on the DN identifier in the DN information, and then the AMF entity determines the SMF entity based on the DN type and the DN identifier. For details, refer to the description of step 204. Details are no longer described here.

Step 304: The AMF entity sends the second message to the SMF entity.

The second message is generated based on the first message, and the second message is used to request the establishment of a PDU session. The second message further includes second DN information. In other words, the second message includes the first message and the second DN information. Also, the AMF entity is unaware of the specific content of the first message.

The second DN information includes a DN identifier, or the second DN information includes a DN identifier and a DN type.

Step 305: The SMF entity determines the PDU session type based on the second message.

After the SMF entity obtains the second DN information, if the second DN information includes the DN identifier, the SMF entity determines the DN type based on the DN identifier, and then determines the PDU session type based on the DN type.

If the second DN information includes a DN identifier and a DN type, the SMF entity obtains the DN type from the second DN information, and then determines the PDU session type based on the DN type.

After block 305, there are two implementations. One of them directly establishes a PDU session, in other words, executes step 306. The other instructs the terminal device to re-initiate the PDU session request process, in other words, executes step 307. These two implementations are described below.

Step 306: The SMF entity establishes a PDU session.

In the previous step 305, the SMF entity determined the session type of the PDU. Thus, the SMF entity can directly establish a session PDU of the session type.

This completes the procedure.

Step 307: The SMF entity sends a session reject message to the terminal using the AMF entity.

To improve the accuracy of the session establishment of the PDU, the SMF entity may optionally send a session reject message to the terminal device using the AMF entity, where the session reject message carries the session type of the PDU, which is determined by the SMF entity, in order for the terminal device to re-initiate the session establishment procedure.

Step 308: The tag sends a third message to the AMF entity and the AMF entity receives the third message from the tag.

Step 309: The AMF entity sends a fourth message to the SMF entity, and the SMF entity receives the fourth message from the AMF entity.

Step 310: The SMF entity establishes a PDU session based on the fourth message.

Steps 308-310 above are similar to steps 208-210 in Embodiment 1. See the descriptions above for details. This document does not re-describe the details.

This completes the procedure.

In steps 301-305 and steps 307-310, the terminal adds the DN to the first message when sending the first message to the AMF entity, then the AMF entity sends the DN to the SMF entity using the second message. After determining the PDU session type, the SMF entity instructs the terminal to re-initiate the third message and the SMF entity receives the fourth message from the AMF entity to accept the correct session type using the fourth message and establish the PDU session. Thus, the correct PDU session type is established.

Optionally, in step 306 or step 310, when establishing a PDU session, the SMF entity establishes a PDU session along with the UPF entity. So the SMF object must also select the UPF object. Optionally, the SMF entity determines the UPF entity based on the DN and the session type of the PDU where the DN may be sent, by the AMF entity, to the SMF entity.

Figure 4 shows a simplified diagram of the device according to the present application. The device may be a terminal device, an AMF entity, or an SMF entity in any of the above embodiments. The device may be a terminal device in the system architecture shown in Fig. 1, or a chip in a terminal device, may be an AMF object in the system architecture shown in Fig. 1, or a chip in an AMF object, or may be an SMF object in the system architecture, shown in figure 1, or a chip in the SMF object.

The device 200 may be configured to perform a method performed by a terminal device, an AMF entity, or an SMF entity in any of the aforementioned session processing methods.

The device 200 includes at least one processing unit 21 and a communication unit 22, and optionally further includes a storage unit 23. The processing unit 21, the communication unit 22 and the storage unit 23 are connected to each other via a communication bus.

The processor 21 may be a general purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to control program execution in accordance with the solutions of the present invention. .

The communication bus may include a path for transferring information between the above blocks.

The communication unit 22 may be a device with a transceiver function and is configured to communicate with another device or communication network, such as Ethernet, radio access network (RAN) or wireless local area network (wireless local area networks, WLAN).

The storage unit 23 may be read-only memory (ROM), another type of static memory capable of storing static information and instructions, random access memory (RAM), or another type of dynamic memory capable of storing information and instructions; or may be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), or other optical disc-based storage device , optical disc storage device (including optical CD, laser disc, optical disc, digital versatile disc, Blu-ray disc or the like), magnetic disc drive, or other magnetic storage device or any other medium, which can be configured to carry or store expected program code in the form of an instruction or data structure, and which can be accessed by a computer. However, the present application is not limited to this. The storage unit 23 may exist independently and may be connected to the processing unit 21 using a communication bus. The storage unit 23 can alternatively be integrated with the processing unit. The storage unit 23 is configured to store the application program code used to execute the solutions of the present invention, and the application program code is executed under the control of the processing unit 21 . The processing unit 21 is configured to execute the application program code stored in the storage unit 23 .

In a specific implementation, in an embodiment, the processing unit 21 may include one or more CPUs, such as CPU 0 and CPU 1 shown in FIG.

In a specific implementation, in an embodiment, the apparatus 200 may include a plurality of processing units, such as the processing unit 21 and the processing unit 28 shown in FIG. Each of the processing units may be a single-core processor (single-CPU) or may be a multi-core processor (multi-CPU). As used herein, a processor may refer to one or more devices, circuitry, and/or a processor core for processing data (eg, computer program instructions).

Optionally, when the device is a terminal device, an AMF entity, or an SMF entity, the processing unit 21 may be, for example, a processor, the communication unit 22 may be, for example, a transceiver, and the transceiver includes RF circuitry. When the device further includes a storage unit 23, the storage unit 23 is configured to store a computer-executable instruction, the processing unit 21 is connected to the storage unit 23, and the processing unit 21 executes the computer-executable instruction stored in the storage unit 23 so that the base station or the terminal device performed the session processing method in any of the above embodiments.

In another possible embodiment, when the device is a chip in a terminal device, a chip in an AMF object, or a chip in an SMF object, the processing unit 21 may be, for example, a processor, and the communication unit 22 may be, for example, an input/output interface, an output, or scheme. The processing unit 21 may execute a machine-executable instruction stored in the storage unit to enable the chip to execute the session processing method in the above embodiment. Optionally, the storage unit is a storage unit located on a chip, such as a register or buffer, or the storage unit may be a storage unit located in a base station or terminal device, but outside the chip, such as a ROM, another type of static memory capable of store static information and instructions, or RAM.

The fact that the chip performs the session processing method can be understood as follows: the chip performs the session processing method together with other components of the device.

For example, when the chip is a chip in a terminal device, the communication unit of the chip is connected to the transceiver of the terminal device. The chip processing unit initiates the APP, determines the PDU session type, generates the first message, and then sends the first message to the terminal device transceiver using the chip communication unit. The terminal transceiver sends the first message to the AMF object. Thus, the chip in the tag implements the session handling method of the embodiments of the present invention.

In another example, when the chip is a chip in an SMF entity, the chip communication unit is connected to the transceiver of the SMF entity. The transceiver of the SMF entity receives the second message from the AMF entity and then sends the second message to the communication unit of the chip. The chip processing unit then sets up a session PDU based on the session type, session PDU, in the second message. Thus, the chip in the SMF object implements the session processing method in the embodiments of the present invention.

In another example, when the chip is a chip in an SMF entity, the chip communication unit is connected to the transceiver of the SMF entity. The transceiver of the SMF entity receives the second message from the AMF entity and then sends the second message to the communication unit of the chip. The chip processing unit then determines the session type of the PDU based on the DN information in the second message. Thus, the chip in the SMF object implements the session processing method in the embodiments of the present invention.

In another example, when the chip is a chip in an AMF entity, the chip's communication unit is connected to the transceiver of the AMF entity. The transceiver of the AMF entity receives the first message and DN information from the terminal device, and then sends the first message and DN information to the communication unit of the chip. The chip processing unit then generates a second message based on the first message, and controls the chip communication unit to send the second message and DN information to the transceiver of the AMF entity. The transceiver of the AMF entity sends the second message and the DN information to the SMF entity. Thus, the chip in the AMF object implements the session processing method in the embodiments of the present invention.

For example, when a device is partitioned in the manner shown in FIG. 4, the processing unit 21 cooperates with the communication unit 22 so that the device can implement the session processing method in any of the above embodiments of the present application.

For example, when the device shown in Figure 4 is a terminal device or a chip in a terminal device,

the processing unit 21 is configured to initiate the APP and determine a session type of a Packet Data Unit (PDU) based on the APP; and

the communication unit 22 is configured to send a first message to an Access and Mobility Management Function (AMF) entity, where the first message includes the session type, and the first message is used to request the establishment of the PDU session type.

In a possible embodiment, the processing unit 21 is specifically configured to:

determining, based on the first match, the session type corresponding to the APP, where

the first match is the match between the APP and the session type of the PDU.

In a possible embodiment, the first correspondence is pre-configured in the terminal device; or

the first match is obtained by the end device from the AMF entity.

In an exemplary embodiment, processor 21 is specifically configured to:

determining, based on the second match, a DN corresponding to the APP;

determining the DN type corresponding to the DN identifier; and

determining, based on the third match, the session type corresponding to the DN type, where

the second match is the match between the APP and the DN, and the third match is the match between the DN type and the session type of the PDU.

In a possible embodiment, the communication unit 22 is additionally configured to:

sending a request message to the AMF object; and

receiving a DN identifier and a DN type that are sent by the AMF entity based on the request message; or

receiving the DN identifier and DN type that are transmitted by the radio access network (RAN) device.

In an exemplary embodiment, the communication unit 22 is further configured to: send the first DN information to the AMF entity, where the first DN information includes the DN identifier or includes the DN identifier and the DN type, the first DN information is used by the AMF entity to determine the SMF entity based on the DN, and the SMF entity is configured to establish the session type of the PDU.

It should be understood that a tag, or a chip in a tag, may be configured to implement the steps performed by the tag in the session processing method of the embodiments of the present invention. Refer to the previous descriptions for explanations of related functions. In this document, the details are not described again.

For example, when the device shown in Fig. 4 is an SMF object or a chip in an SMF object,

the communication unit 22 is configured to receive a second message from an Access and Mobility Management Function (AMF) entity, where the second message includes a Packet Data Unit (PDU) session type requested by the terminal, and the second message is used to request the establishment of a PDU session; and

the processing unit 21 is configured to establish a PDU session based on the PDU session type.

Optionally, the communication unit 22 is further configured to receive the DN from the AMF object; and

the processing unit 21 is further configured to determine a user plane function (UPF) object based on the DN and the PDU session type, where the UPF object is configured to establish the PDU session type.

It should be understood that the SMF entity or the chip in the SMF entity may be configured to implement the steps performed by the SMF entity in the session processing method in the embodiments of the present invention. Refer to the previous descriptions for explanations of related functions. In this document, the details are not described again.

For example, when the device shown in Fig. 4 is an SMF object or a chip in an SMF object,

the communication unit 22 is configured to receive a second message from an access and mobility management function (AMF) entity, where the second message includes second data network (DN) information, and the second message is used to request a PDU session; and

the processing unit 21 is configured to determine the PDU session type based on the second DN information.

Optionally, the second DN information includes a DN identifier, and the processing unit 21 is specifically configured to:

determining a DN type based on the DN identifier and determining a PDU session type based on the DN type; or

the second DN information includes the DN type, and the processing unit 21 is specifically configured to determine the PDU session type by the SMF entity based on the DN type.

Optionally, if the second message carries the session type of the session PDU requested by the end device, when the session type of the PDU, which is determined by the processing unit 21 based on the second DN information, is incompatible with the session type of the session PDU requested by the end device, block 22 communication is configured to send a session reject message to the terminal, where the session reject message includes a PDU session type that is determined by the processing unit 21 based on the second DN information.

In a possible embodiment, the processing unit 21 is additionally configured to:

establishing a PDU session based on the PDU session type.

In a possible embodiment, the processor 21 is additionally configured to:

determining a user plane function (UPF) object based on the second DN information; and

establishing the session type of the PDU with the UPF object.

It should be understood that the SMF entity or the chip in the SMF entity may be configured to implement the steps performed by the SMF entity in the session processing method in the embodiments of the present invention. Refer to the previous descriptions for explanations of related functions. In this document, the details are not described again.

For example, when the device shown in Fig. 4 is an AMF object or a chip in an AMF object,

the communication unit 22 is configured to receive the first message and the DN information of the first communication network from the terminal device, where the first message is used to request the establishment of a PDU session; and

the processing unit 21 is configured to: determine a session management function (SMF) object based on the first DN information; and sending a second message to the SMF entity based on the first message, where the second message is used to request the establishment of a session PDU and the session type of the PDU matches the first DN information.

Optionally, the first message and the second message include the session type, session PDU, requested by the terminal; or

the first DN information includes a DN ID, the second message includes a DN ID, and the DN ID is used by the SMF entity to determine the PDU session type based on the DN ID.

Optionally, the first DN information includes a DN identifier, and the communication unit 22 is further configured to receive a data network (DN) identifier from the terminal device;

the processing unit 21 is specifically configured to determine the DN type based on the DN; and

the communication unit 22 is further configured to: send the DN identifier and the DN type to the NRF object; and receiving an SMF object from the NRF object, where the SMF object is determined by the NRF object based on the DN identifier and the DN type.

In a possible embodiment, the communication unit 22 is additionally configured to:

receiving a registration request message from the terminal device;

obtaining, from the database based on the registration request message, DN information to which the terminal is subscribed, the signed DN information including a DN identifier and a DN type; and

transmitting, to the end device, the DN information to which the end device is subscribed.

In an exemplary embodiment, the registration request message includes terminal capability indication information, where the capability indication information is used to indicate a data network supported by the terminal; and

the DN information subscribed to by the end device corresponds to the data network supported by the end device.

It should be understood that the AMF entity or chip in the AMF entity may be configured to implement the steps performed by the AMF entity in the session processing method in the embodiments of the present invention. Refer to the previous descriptions for explanations of related functions. In this document, the details are not described again.

The present application further provides for a computer-readable storage medium. The computer-readable storage medium stores an instruction that, when executed on a computer, causes the computer to perform operations performed by a terminal device in the above session processing method. The computer may be a terminal device.

The present application further provides for a computer-readable storage medium. The computer-readable storage medium stores an instruction that, when executed on a computer, causes the computer to perform operations performed by the SMF object in the above session processing method. A computer can be an SMF object.

The present application further provides for a computer-readable storage medium. The computer-readable storage medium stores an instruction that, when executed on a computer, causes the computer to perform operations performed by the AMF object in the above session processing method. The computer can be an AMF object.

The present application provides a computer program product. The computer program product includes a computer software instruction, and the computer software instruction may be loaded by a processor to implement a procedure of the session processing method performed by the terminal in any of the above embodiments.

The present application provides a computer program product. The computer program product includes a computer software instruction, and the computer software instruction may be loaded by a processor to implement a procedure of the session processing method performed by the SMF entity in any of the above embodiments.

The present application provides a computer program product. The computer program product includes a computer software instruction, and the computer software instruction may be loaded by a processor to implement a procedure of the session processing method performed by the AMF entity in any of the above embodiments.

As described above for this specification in this application, techniques in the art may use or implement the content of this application. Any modification based on the disclosed content should be considered obvious in the art. The basic principles described in this application may be applied to other embodiments without departing from the spirit and scope of this application. Thus, the content disclosed in this application is not limited to the described embodiments and variants, but can also be expanded to the maximum extent that is consistent with the principles and disclosed new features of the present application.

Claims (45)

1. A method for processing a session, comprising the steps of: initiating, with the help of the terminal device, the application APP; determining, by the terminal, based on a UE route selection policy (URSP), a session type corresponding to the APP, wherein the URSP contains a mapping between the APP and the session type; and transmitting, by the terminal, a first message to an Access and Mobility Management Function (AMF) entity, the first message carrying a session type, and the first message being used to request a session establishment of said session type. 2. The method of claim 1, wherein the session is a session PDU. 3. The method of claim 1 or 2, wherein the session type comprises an Ethernet type. 4. The method according to claim 1 or 2, further comprising the step of: determining, by the terminal, based on the URSP, a data network (DN) corresponding to the APP. 5. The method of claim 4, further comprising the step of: transmitting, by the end device, the first DN information to the AMF entity, wherein the first DN information contains the DN identifier for the DN or contains the DN identifier and the DN type for the DN, the first DN information is used by the AMF entity to determine the Session Management Function (SMF) entity, wherein the SMF entity is configured to establish a session. 6. The method of claim 5, further comprising, when the session type is the first session type, the step of: receiving, by the terminal, a session reject message, wherein the session reject message comprises a second session type. 7. The method of claim 6, further comprising the step of: transmitting, by means of the terminal, a third message to the AMF object, wherein the third message contains the second session type and the third message is used to request a session setup of the second session type. 8. A session processing method, further comprising the steps of: receiving, with the help of a session management function (SMF) entity, a second message from an access and mobility management function (AMF) entity, wherein the second message carries the second data network DN information and the session type requested by the terminal, and the second message is used to request establishing a session corresponding to the session type requested by the end device, wherein the session type requested by the end device corresponds to the APP initiated by the end device and is determined, by the end device, based on the UE route selection policy (URSP), while the URSP contains the mapping between APPs and session type; determining, using the SMF object, based on the second DN information, a session type corresponding to the second DN information; and sending, by means of the SMF object, to the terminal device a session reject message when the session type corresponding to the second DN information does not match the session type requested by the terminal device, wherein the session reject message contains the session type corresponding to the second DN information. 9. The method of claim 8, wherein the session is a PDU session. 10. The method of claim 8 or 9, wherein the type of session requested by the terminal comprises an Ethernet type. 11. The method according to claim 8 or 9, in which, when the second DN information contains the DN, the step of determining, by the SMF object, based on the second DN information, the type of session corresponding to the second DN information, contains sub-steps of: determining, using the SMF object, the type of the DN based on the DN, and determining the type a session corresponding to the second DN information based on the DN type; or when the second DN information contains the DN type, the step of determining, by the SMF object, based on the second DN information, the session type corresponding to the DN information, contains a sub-step of: determining, by the SMF object, the session type corresponding to the second DN information based on the type DN. 12. A session processing device, comprising a processing unit and a communication unit, wherein the processing unit is configured to initiate the APP and determine the session type corresponding to the APP based on the UE route selection policy (URSP), wherein the URSP contains a correspondence between the APP and the session type; a the communication unit is configured to send a first message to an access and mobility management function (AMF) entity, the first message containing a session type, and is used to request a session setup of said session type. 13. The apparatus of claim 12, wherein the session is a session PDU. 14. The apparatus of claim 12 or 13, wherein the session type comprises an Ethernet type. 15. The method of claim 12 or 13, wherein the processing unit is further configured to determine a data network (DN) corresponding to the APP based on the URSP. 16. The apparatus of claim 15, wherein the communication unit is further configured to: transmitting the first DN information to the AMF object, wherein the first DN information contains a DN identifier for the DN or contains a DN identifier and a DN type for the DN, and is used by the AMF object to determine a session management function (SMF) object, and the SMF object is configured to establish a session. 17. The apparatus of claim 16, wherein when the session type is a first session type, the communication unit is further configured to receive a session reject message, wherein the session reject message comprises a second session type. 18. The apparatus of claim 17, wherein the communication unit is further configured to send a third message to the AMF entity, wherein the third message contains a second session type and the third message is used to request a session setup of the second session type. 19. A session processing device, comprising a processing unit and a communication unit, wherein the communication unit is configured to receive a second message from an access and mobility management function (AMF) entity, wherein the second message carries information of the second data network (DN) and the session type requested by the terminal device, and is used to request a session setup corresponding to the session type requested by the terminal device, wherein the session type requested by the terminal device corresponds to the APP initiated by the terminal device and is determined by the terminal device based on the UE's route selection policy (URSP), wherein the URSP contains the correspondence between APP and session type; and the processing unit is configured to determine, based on the second DN information, a PDU session type based on the second DN information corresponding to the second DN information; wherein the communication unit is further configured to send, to the terminal, a session reject message when the session type corresponding to the second DN information does not match the session type requested by the terminal, wherein the session reject message contains the session type corresponding to the second DN information. 20. The apparatus of claim 19, wherein the session is a PDU session. 21. The apparatus of claim 19 or 20, wherein the session type requested by the terminal contains an Ethernet type. 22. The apparatus of claim 19 or 20, wherein the second DN information comprises a DN identifier, and the processing unit is specifically configured to: determine a DN type based on the DN identifier and determine a PDU session type corresponding to the second DN information based on the DN type ; or the second DN information contains the DN type, and the processing unit is specifically configured to: determine the session type corresponding to the second DN information based on the DN type. 23. A session processing chip system, comprising at least one processor and an interface circuit, wherein the interface circuit and at least one processor are connected to each other using a line, and the processor is configured to execute instructions for implementing the method according to any one of claims .1-7. 24. A session processing chip system, comprising at least one processor and an interface circuit, wherein the interface circuit and at least one processor are connected to each other using a line, and the processor is configured to execute instructions for implementing the method according to any one of claims .8-11. 25. A computer-readable storage medium containing instructions causing, when executed on a computer, the computer to execute the method according to any one of claims 1-7. 26. A computer-readable storage medium containing instructions causing, when executed on a computer, the computer to execute the method according to any one of claims 8-11.

Images