CN110121897B

CN110121897B - Method and equipment for establishing session

Info

Publication number: CN110121897B
Application number: CN201780081592.6A
Authority: CN
Inventors: 杨皓睿; 金辉; 欧阳国威; 窦凤辉; 李小娟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-08-15
Filing date: 2017-08-15
Publication date: 2021-09-17
Anticipated expiration: 2037-08-15
Also published as: CN110121897A; WO2019033269A1

Abstract

The embodiment of the application relates to a method and equipment for session establishment. The method specifically comprises the following steps: the UE may indicate to the AMF entity whether the PDU session requested to be established supports inter-access technology handover, so that the AMF entity determines whether to update the DNN to the UDM entity according to a registration condition of the UE when determining that the PDU session supports inter-access technology handover. Alternatively, the UE may directly determine whether the PDU session supports inter-access technology handover and the registration condition of the UE, and when both satisfy the condition, instruct the SMF entity to register the DNN and the information of the SMF entity with the UDM entity. Therefore, the SMF entity updates DNN to the UDM entity under not all conditions, and signaling resources are saved.

Description

Method and equipment for establishing session

Technical Field

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

Background

In a 5G network, User Equipment (UE) may register in a core network via the third generation partnership project (3 GPP) access technology and Non-3GPP access technology. For example, the Non-3GPP access technology may be a Wireless Local Area Network (WLAN) technology. During registration, an access and mobility management entity (AMF) updates an AMF ID and an address currently registered by the UE to a Unified Data Management (UDM) entity, and the UDM entity stores an AMF ID and/or an address corresponding to each access technology type (AT type).

When the UE needs to use the service, it will perform Protocol Data Unit (PDU) session establishment through the corresponding access technologies. Also, the UE may choose to hand over a PDU session that has been established over one access technology to another access technology.

And when the PDU session is switched, the UDM entity informs the AMF entity registered by the UE of the subscription information of the UE after the PDU session is switched. However, the Session Management Function (SMF) entity and the UDM entity do not know the access technology used by the UE in the PDU session handover process, and when the information corresponding to the PDU session is updated, all the AMF entities registered by the access technology used by the current PDU session are notified, but the AMF entities registered by the access technology used by the current PDU session do not need to be updated, which wastes signaling.

Disclosure of Invention

The embodiment of the application provides a session establishment method and equipment. Therefore, less signaling resources are occupied in the session establishment process.

In a first aspect, an embodiment of the present application provides a session establishment method. The method comprises the following steps: the UE sends a first message to an AMF entity, for example, the first message may be a Non-Access Stratum (NAS) message; the first message includes first information, which may be, for example, N1 Session Management (SM) information; the first information includes information requesting establishment of a PDU session, the information requesting establishment of a PDU session includes a first parameter, for example, the first parameter may be a handover indication; the first parameter is used to indicate that the PDU session supports handover between different access technologies, for example, between a 3GPP access technology and a non-3GPP access technology. Or, the first parameter is used to indicate a Data Network Name (DNN) used by the SMF entity to register the PDU session with the UDM entity and information of the SMF entity, where the information of the SMF entity includes an identifier and/or an address of the SMF entity. The UE receives a second message sent by the AMF entity, where the second message includes second information, for example, the second information may be N1SM information, and the second information includes PDU session establishment accept information. Through the embodiment of the application, the UE can indicate whether the PDU session requested to be established supports the switching between the access technologies to the AMF entity, so that when the AMF entity determines that the PDU session supports the switching between the access technologies, whether the DNN needs to be updated to the UDM entity is determined according to the registration condition of the UE. Alternatively, the UE may directly determine whether the PDU session supports inter-access technology handover and the registration condition of the UE, and when both satisfy the condition, instruct the SMF entity to register the DNN and the information of the SMF entity with the UDM entity. Therefore, the SMF entity updates the information to the UDM entity under not all conditions, or the DNN corresponding to the UE is not updated under all conditions when the SMF entity updates the UDM entity, so that the signaling resource is saved. In addition, the SMF entity may further determine, according to the indication of the first parameter of the UE, whether the UDM entity needs to update the subscription information of the UE to another AMF entity, so that the UDM entity updates the subscription information of the UE to another AMF entity when determining that there is another AMF entity registered by the UE through another access technology in combination with the information sent by the SMF entity.

In an optional implementation, before the UE sends the first message to the AMF entity, the method further includes: the UE determines the first parameter according to at least one of a user equipment policy or a service. By the embodiment of the application, the UE can judge whether one PDU session supports switching between access technologies according to the access type in the user equipment strategy, or determine whether the PDU session corresponding to the service flow supports switching between different access technologies according to a specific service flow, such as a service flow identifier.

In another alternative implementation, the UE determines the first parameter when the access type in the UE policy indicates multiple access technologies, or the UE policy does not define the access type. For example, when the access type in the UE policy indicates a 3GPP access technology and a non-3GPP access technology, the UE determines a first parameter, where the first parameter is used to indicate that the PDU session supports handover between the 3GPP access technology and the non-3GPP access technology. The method and the device can realize that whether the PDU session supports the switching between the access technologies is determined according to the access type in the user equipment strategy.

In another optional implementation, the UE sends a first message to the AMF entity, where the first message includes first information, where the first information includes information requesting to establish a PDU session, and the information requesting to establish the PDU session includes a first parameter, where the first parameter is used to indicate that the SMF entity registers, with the UDM entity, a DNN used by the PDU session and an identity and/or address of the SMF entity, and specifically includes: when the UE is registered by one access technology or the UE is registered by multiple access technologies and the registered AMF entities are different, the UE sends a first message to the AMF entity, wherein the first message comprises first information, the first information comprises information for requesting to establish a PDU session, and the information for requesting to establish the PDU session comprises a first parameter, and the first parameter is used for indicating the DNN used by the PDU session registered by the SMF entity to the UDM entity and the information of the SMF entity. According to the embodiment of the application, when the UE determines that the UE is registered through one access technology or through multiple access technologies and registered in different AMF entities, the UE sends the first message carrying the first parameter to the AMF entities, and the signaling resource occupation is small.

Through the embodiment of the application, the UE can indicate whether the PDU session requested to be established supports the switching between the access technologies to the AMF entity, so that when the AMF entity determines that the PDU session supports the switching between the access technologies, whether the DNN needs to be updated to the UDM entity is determined according to the registration condition of the UE. Alternatively, the UE may directly determine whether the PDU session supports inter-access technology handover and the registration condition of the UE, and when both satisfy the condition, instruct the SMF entity to register the DNN and the information of the SMF entity with the UDM entity. Therefore, the SMF entity updates the information to the UDM entity under not all conditions, or the SMF entity updates the DNN under not all conditions when updating to the UDM entity, so that the signaling resource is saved. In addition, the SMF entity may also determine, according to the indication of the first parameter of the UE, whether the UDM entity needs to update the subscription information of the UE to another AMF entity, so that the UDM entity, in combination with the information sent by the SMF entity, determines that there is another AMF entity registered by the UE through another access technology, and updates the subscription information of the UE to the other AMF entity, thereby saving signaling resources.

In a second aspect, an embodiment of the present application provides a session establishment method. The method comprises the following steps: the AMF entity receives a first message sent by the UE, wherein the first message comprises first information, the first information comprises information requesting to establish a PDU session, the information requesting to establish the PDU session comprises a first parameter, the first parameter is used for indicating that the PDU session supports switching between different access technologies, or indicating that the SMF entity registers DNN used by the PDU session with the UDM entity and the information of the SMF, and the information of the SMF comprises the identification and/or address of the SMF entity; the AMF entity sends a request for calling the first service of the SMF entity to the SMF entity, wherein the request for calling the first service of the SMF entity comprises first information; the AMF entity receives a response which is sent by the SMF entity and used for calling the first service of the SMF entity, wherein the response which is sent by the SMF entity and used for calling the first service of the SMF entity comprises second information, and the second information comprises a PDU session establishment acceptance message; the AMF entity transmits a fourth message to the UE, the fourth message including the second information. According to the embodiment of the application, when the AMF entity receives the PDU session supporting switching among the access technologies sent by the UE and indicating that the PDU session requested to be established by the UE supports switching among the access technologies, the AMF entity determines whether to update DNN to the UDM entity according to the registration condition of the UE. Or, the UE may directly determine whether the PDU session supports inter-access technology handover and a registration condition of the UE, and when both of them satisfy the condition, instruct the SMF entity to register information of the DNN and the SMF entity with the UDM entity through the AMF. Therefore, the SMF entity updates the information to the UDM entity not under all conditions, or when the SMF entity updates to the UDM entity, DNN is not updated under all conditions, and the UE does not send NAS information carrying the first parameter under all conditions, so that signaling resources are saved.

In an optional implementation, after the receiving, at the AMF entity, a first message sent by the UE, the first message including first information, the first information including information requesting to establish a PDU session, the information requesting to establish the PDU session including a first parameter, and the first parameter being used to indicate that the PDU session supports handover between different access technologies, the method further includes: the AMF entity determines a second parameter indicating that the UE is registered in the AMF through one access technology. At this time, the AMF entity sends a request for invoking the first service of the SMF entity to the SMF entity, where the request for invoking the first service of the SMF entity includes first information, which specifically includes: the AMF entity sends a request for calling the first service of the SMF entity to the SMF entity, wherein the request for calling the first service of the SMF entity comprises first information and second parameters. According to the embodiment of the application, when the AMF entity receives a first message sent by the UE, the AMF determines the registration condition of the UE, and when the AMF determines that the UE is registered on the AMF through one access technology, the AMF sends a request which comprises a first parameter and a second parameter and calls a first service of the SMF entity to the SMF entity. In other cases, the request for invoking the first service of the SMF entity sent to the SMF entity does not need to carry the second parameter, thereby saving signaling.

According to the embodiment of the application, when receiving the PDU session supporting switching among access technologies sent by the UE and indicating that the PDU session requested to be established by the UE supports switching among the access technologies, the AMF entity determines whether to update DNN to the UDM entity according to the registration condition of the UE. Or, the UE may directly determine whether the PDU session supports inter-access technology handover and a registration condition of the UE, and when both of them satisfy the condition, instruct the SMF entity to register information of the DNN and the SMF entity with the UDM entity through the AMF. Therefore, the SMF entity updates the DNN to the UDM entity not under all conditions, and the UE does not send NAS messages carrying the first parameter under all conditions, so that signaling resources are saved.

In a third aspect, an embodiment of the present application provides a session establishment method. The method comprises the following steps: the method comprises the steps that an SMF entity receives a request for calling a first service of the SMF entity, wherein the request for calling the first service of the SMF entity comprises first information, the first information comprises information for requesting to establish a PDU session, the information for requesting to establish the PDU session comprises a first parameter, the first parameter indicates that the PDU session supports switching between different access technologies, or indicates that the SMF entity registers DNN (direct to network) used by the PDU session and information of the SMF to a UDM (universal data management) entity, and the information of the SMF entity comprises identification and/or address of the SMF entity; the SMF entity transmits a response to the first AMF entity invoking the first service of the SMF entity, the response to invoke the first service of the SMF entity including second information including PDU session setup accept information. According to the embodiment of the application, the SMF entity sends the information to the UDM entity after receiving the corresponding indication, or updates the DNN when the SMF entity updates the UDM entity after receiving the corresponding indication, so that the signaling resource is saved.

In an optional implementation, when the first parameter indicates that the PDU session supports handover between different access technologies, the request for invoking the first service of the SMF entity further includes a second parameter indicating that the UE establishing the PDU session is registered in the first AMF through one access technology. According to the embodiment of the application, the SMF determines that the UE supports switching among different access technologies, and only one access technology is registered on the current AMF entity, at the moment, the SMF entity updates subscription information of the UE to the UDM entity, and the subscription information of the UE comprises DNN.

In another optional implementation, the method further comprises: the SMF entity sends a request for invoking the first service of the UDM entity to the UDM entity, wherein the request for invoking the first service of the UDM entity comprises the DNN used by the PDU session and the information of the SMF entity.

According to the embodiment of the application, the SMF updates the UDM entity after receiving the corresponding indication, or the SMF entity sends the DNN to the UDM entity after receiving the corresponding indication, so that the signaling resource is saved.

In a fourth aspect, an embodiment of the present application provides a session establishment method. The method comprises the following steps: the method comprises the steps that a UDM entity receives a request for calling a first service of the UDM entity, wherein the request for calling the first service of the UDM entity comprises an access type, and the access type is used for indicating UE (user equipment) corresponding to a PDU (protocol data Unit) session managed by the SMF entity to register in a first AMF entity through a first access technology; and the UDM entity determines a second AMF entity registered by the UE by using a second access technology according to the access type, if the second AMF entity exists, the UDM entity calls a second service of the UDM entity and informs the second AMF entity to update the stored subscription data of the UE, wherein the subscription data of the UE comprises the information of the SMF entity and the DNN used by the PDU session managed by the SMF entity, and the information of the SMF entity comprises the identification and/or address of the SMF entity.

By the embodiment of the application, the UDM entity can determine that the UE is registered in different AMF entities through different access technologies according to the access type, and the UDM entity can update subscription data of the UE to the AMF entities except for the current AMF entity.

In a fifth aspect, there is provided a UE having functionality to implement the UE behaviour in the above first aspect and optionally in its implementation. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. Through the embodiment of the application, the UE can indicate whether the PDU session requested to be established supports the switching between the access technologies to the AMF entity, so that when the AMF entity determines that the PDU session supports the switching between the access technologies, whether the DNN needs to be updated to the UDM entity is determined according to the registration condition of the UE. Or, the UE may directly determine whether the PDU session supports inter-access technology handover or not, and a registration condition of the UE, and when both of them meet a condition, instruct the SMF entity to register DNN and information of the SMF entity with the UDM entity, where the information of the SMF entity includes an identity and/or an address of the SMF entity. Therefore, the SMF entity updates the information to the UDM entity under not all conditions, or when the SMF entity updates the UDM entity, DNN is not updated under all conditions, and signaling resources are saved. In addition, the SMF entity may also determine, according to the indication of the first parameter of the UE, whether the UDM entity needs to update the subscription information of the UE to another AMF entity, so that the UDM entity, in combination with the information sent by the SMF entity, determines that there is another AMF entity registered by the UE through another access technology, and updates the subscription information of the UE to the other AMF entity, thereby saving signaling resources.

In a sixth aspect, there is provided an AMF entity having the functionality to implement the AMF entity behaviour of the second aspect above and in its optional implementation. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. According to the embodiment of the application, when the AMF entity receives the PDU session supporting switching among the access technologies sent by the UE and indicating that the PDU session requested to be established by the UE supports switching among the access technologies, the AMF entity determines whether to update DNN to the UDM entity according to the registration condition of the UE. Or, the UE may directly determine whether the PDU session supports inter-access technology handover and a registration condition of the UE, and when both of them satisfy the condition, instruct the SMF entity to register information of the DNN and the SMF entity with the UDM entity through the AMF. Therefore, the SMF entity updates the information to the UDM entity not under all conditions, or when the SMF entity updates the UDM, the DNN is not updated under all conditions, and the UE does not send the NAS message carrying the first parameter under all conditions, so that signaling resources are saved.

In a seventh aspect, there is provided an SMF entity having functionality to implement the SMF entity behaviour in the third and optionally also implementations described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. According to the embodiment of the application, the SMF sends the DNN to the UDM entity after receiving the corresponding indication, so that signaling resources are saved.

In an eighth aspect, there is provided a UDM entity having functionality to implement the UDM entity behaviour in the third and optionally also implementations described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions. According to the embodiment of the application, the UDM entity can be determined according to the access type, and when the UE is registered in different AMF entities through different access technologies, the UDM entity can update the subscription data of the UE to the AMF entities except the current AMF entity.

In a ninth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of any one or more of the first, second, third and fourth aspects described above.

In a tenth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one or more of the first, second, third and fourth aspects described above.

Through the embodiment of the application, the UE may indicate to the AMF entity whether the PDU session requested to be established supports inter-access technology handover, so that when the AMF entity determines that the PDU session supports inter-access technology handover, it is determined whether information needs to be updated to the UDM entity according to a registration condition of the UE, or when the SMF entity updates to the UDM entity, it is determined whether DNN needs to be updated. Alternatively, the UE may directly determine whether the PDU session supports inter-access technology handover and the registration condition of the UE, and when both satisfy the condition, instruct the SMF entity to register the DNN and the information of the SMF entity with the UDM entity. Therefore, the SMF entity updates the information to the UDM entity under not all conditions, or the DNN is not updated under all conditions when the SMF entity updates the UDM entity, so that the signaling resource is saved. In addition, the SMF entity may also determine, according to the indication of the first parameter of the UE, whether the UDM entity needs to update the subscription information of the UE to another AMF entity, so that the UDM entity, in combination with the information sent by the SMF entity, determines that there is another AMF entity registered by the UE through another access technology, and updates the subscription information of the UE to the other AMF entity, thereby saving signaling resources. The SMF sends DNN to the UDM entity after receiving corresponding indication, thus saving signaling resources. The UDM entity may determine, according to the access type, that the UE is registered in different AMF entities through different access technologies, and update subscription data of the UE to the AMF entities other than the current AMF entity.

Drawings

Fig. 1 is a schematic structural diagram of a 5G communication network according to an embodiment of the present disclosure;

fig. 2 is a schematic structural diagram of another 5G communication network provided in an embodiment of the present application;

fig. 3 is a schematic signaling interaction diagram of a session establishment method according to an embodiment of the present application;

fig. 4 is a schematic signaling interaction diagram of another session establishment method according to an embodiment of the present application;

fig. 5 is a signaling interaction example of a session establishment method according to an embodiment of the present application;

fig. 6 is a signaling interaction example of another session establishment method provided in the embodiment of the present application;

fig. 7 is a schematic structural diagram of a UE according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of an AMF entity according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an SMF entity provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of a UDM entity according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of another UE provided in the embodiment of the present application;

fig. 12 is a schematic structural diagram of another AMF entity provided in the embodiment of the present application;

fig. 13 is a schematic structural diagram of another SMF entity provided in the embodiment of the present application;

fig. 14 is a schematic structural diagram of another UDM entity provided in the embodiment of the present application.

Detailed Description

The embodiments of the present application will be described below with reference to the drawings.

The embodiment of the application provides a method and equipment for session establishment, which are applied to a 5G communication network.

In embodiments of the present application, a user device may also be referred to as a terminal (terminal), which may refer to a device that provides voice and/or data connectivity to a user, a handheld device having wireless connection capability, or other processing device connected to a wireless modem. Wireless terminals, which may be mobile terminals such as mobile telephones (or "cellular" telephones) and computers having mobile terminal equipment, e.g., portable, pocket, hand-held, computer-included, or vehicle-mounted mobile devices, may communicate with one or more core networks via the RAN, and may exchange language and/or data with a radio access network. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. A wireless terminal may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal (remote terminal), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), a user equipment (user device), or a user equipment (user equipment), which is not limited in the embodiments of the present application. According to the service type division, the UE related to the embodiment of the present invention may be a terminal device having higher requirements for speed and mobility in the foregoing, such as a mobile phone, a multimedia device, and the like, or a terminal of the internet of things, or a terminal of the internet of vehicles.

A network slice is implemented into a network deployment as a Network Slice Instance (NSI). One network slice may implement multiple network slice instances.

Fig. 1 is a schematic structural diagram of a 5G communication network according to an embodiment of the present application. Fig. 2 is a schematic structural diagram of another 5G communication network provided in the embodiment of the present application.

In the embodiment of the present application shown in fig. 1 and fig. 2, the AMF entity, the SMF entity, the UDM entity, and the User Plane Function (UPF) entity may be one or more servers in a core network of the 5G communication network. The UE may communicate with a core network of the 5G communication network via a 3GPP access technology or a non-3GPP access technology. For example, the UE may Access a core Network of the 5G communication Network through an Evolved Node B (eNB) or through a Radio Access Network (RAN), and the UE may also Access the core Network of the 5G communication Network through a Wireless-Fidelity (Wi-Fi) technology and a non-3GPP inter-working function (N3 IWF) entity to perform communication. Wherein, the access is performed through an eNB through an evolved-universal terrestrial Radio access (E-UTRA) technology, or through a RAN through a New Radio technology (NR), which may be considered as the access through a 3GPP access technology; access over Wi-Fi technology may be considered access over non-3GPP access technologies.

The functions of the respective modules in the 5G communication network are briefly described below.

The AMF entity has the functions of mobility management, registration management, connection management, lawful interception, support of transmitting SM information between the UE and the SMF entity, access authentication, access authorization and the like of the UE.

The SMF entity has the functions of session management, roaming and the like. Among them, session management functions, such as session establishment, modification, and release, include UPF and Access Network (AN) node (node) tunnel maintenance. Roaming functions may include charging data collection, signaling to support authentication/authorization with an external Data Network (DN).

The UPF entity has the functions of data packet routing, lawful interception and the like.

The UDM entity has the functions of certificate authentication, user identification, access authorization, registration and mobility management, subscription management, short message management and the like.

The N3IWF entity has the functions of relaying signaling of uplink and downlink between the UE and the AMF entity, relaying user plane data packets of the uplink and downlink between the UE and the UPF entity, and supporting AMF selection.

The UE is connected with the RAN through a Uu interface; the signaling and data between the RAN equipment and the AMF entity are connected through an N2 interface; the signaling and data between the AMF entity and the SMF entity are transmitted through an N11 interface; signaling and data between the SMF entity and the UPF entity are transmitted through N4. It should be noted that the definitions of the Uu interface, the N2 interface, the N3 interface, the N11 interface, and the N4 interface may specifically refer to the 3GPP standard.

As shown in fig. 1, when the UE is registered in the 5G network, it may be registered in the same AMF entity through the 3GPP access technology and the non-3GPP access technology.

As shown in fig. 2, when the UE is registered in the 5G network, it may also be registered in different AMF entities through a 3GPP access technology and a non-3GPP access technology. Fig. 2 shows that the 3GPP access technology and the N3GPP access technology are respectively registered in different Public Land Mobile Networks (PLMNs), and the SMF entity in the embodiment is an SMF entity of the HPLMN.

Of course, when the UE is registered in the 5G network, the UE may also be registered in the AMF entity only through the 3GPP access technology or the non-3GPP access technology.

Wherein, when the UE is registered in the same AMF entity through the 3GPP access technology and the non-3GPP access technology, the PDU session of the UE needs to be switched from one access technology to another access technology.

To ensure traffic continuity, the IP address used by a PDU session needs to be guaranteed to be unchanged when the PDU session is handed over to another access technology. To achieve this, when the UE initiates handover of a PDU session to the AMF entity, the AMF entity needs to select an SMF entity used before the PDU session. Since the SMF entity holds the IP address of the PDU session, selecting the same SMF entity can ensure that the IP address of the PDU session is unchanged.

For example, when the UE establishes a PDU session on 3GPP, the AMF entity stores the correspondence between the session ID and the SMF ID and/or address, and the SMF entity stores the correspondence between the session ID and the IP address. When the UE initiates PDU session handover, i.e. PDU session reestablishment, on non-3GPP, the UE carries the same session ID. Because the AMF entities are the same, the AMF entity may find the same SMF according to the correspondence between the session ID and the SMF ID and/or address that have been saved. After receiving the PDU session establishment request, the SMF uses the same IP address for the UE according to the corresponding relation between the session ID and the IP address kept in the SMF.

For another example, when the UE registers different AMFs through two access technologies, because the AMF entities registered through the 3GPP access technology and the N3GPP technology are different, when PDU session handover is performed, the AMF entity selects the same SMF through the SMF ID/address included in the UE subscription data notified by the UDM.

With reference to the drawings, a PDU session establishment (reestablishment) method performed by a UE when the UE is registered with only one access technology, or the UE is registered with multiple access technologies but the registered AMF entities are different, will be further described.

Fig. 3 is a schematic signaling interaction diagram of a session establishment method according to an embodiment of the present application. As shown in fig. 3, the method specifically includes the following steps:

s310, the UE transmits a first message to the first AMF entity. The first message comprises first information, the first information comprises information requesting to establish the PDU session, and the information requesting to establish the PDU session comprises first parameters. The first message may be an NAS message, the information requesting to establish the PDU session is used to request to establish the PDU session from the SMF entity, and the first parameter is used to indicate that the PDU session supports handover between different access technologies.

The UE may determine whether the PDU session supports inter-access technology handover based on at least one of user equipment policy or traffic.

For example, when the UE successfully registers in the 5G network, a user equipment policy (UE policy) issued by the network, for example, a UE routing policy (URSP) may be received. The UE decides from the URSP that the data uploaded by the application should be transferred on a PDU session that satisfies the conditions. If there is already a PDU session that satisfies the conditions, it is transmitted over it, and if not, the UE initiates PDU session establishment.

The UE may determine whether the PDU session supports inter-access technology handover according to a parameter corresponding to an Access Type (AT) in a URSP rule sent by the first AMF entity to the UE when the UE is registered in the first AMF entity. As an example, the URSP rules can be seen in table 1.

TABLE 1

Wherein, the flow sifter: information that can be compared to the data stream and determine whether the rule applies to the data stream. It may include application identifiers and other information for the data streams it is adapted for. The data stream that matches the stream filter of the URSP rule is called a "matching stream", which is the "matching stream" of the URSP rule.

Direct shunting: indicating that non-3gpp access outside of the PDU session is preferred or allowed (i.e., allowed but not preferred) if the matching flow is barred. It may also indicate a specific non-3GPP access type (e.g., WLAN, ssid-x) in which matching flows are forbidden, preferred or allowed.

Slice information: this includes matching the S-NSSAI required for the flow. If the matching stream can support these S-NSSAIs through one PDU session, it may also include multiple S-NSSAIs. It is used to associate the matching stream with one or more S-NSSAIs. When S-NSSAI is not available, the UE also uses this information to select a matching stream to replace the currently used S-NSSAI.

The continuity type: this includes the SSC pattern required for the matching stream. If a matching flow can support any one SSC pattern through one PDU session, it may also contain multiple SSC patterns in a priority order. It is used to associate matched traffic with one or more SSC patterns.

DNNs: this includes matching the DNN required for the stream. It is also possible to include multiple priority DNNs if the matching flow can be transferred to these DNNs via PDU sessions. It is used to associate matching streams with one or more DNNs.

And (3) access type: if the UE needs to establish a PDU session for the matching flow, it indicates the access type (3GPP or non-3 GPP) that the PDU session should be established. It may also indicate a priority access list that PDU session setup should be attempted. Wherein, the parameter corresponding to the access type directly indicates the 3GPP access and the N3GPP access, and then it is considered to support the handover between different access technologies, or the URSP rule does not limit the access type, for example, the parameter without the access type in the URSP rule is the default to support the handover between different access technologies.

According to the information provided in table 1, it can be determined that the PDU session corresponding to "DummyApp" only allows for establishment through 3GPP access technology, that is, the PDU session corresponding to "DummyApp" does not support inter-access technology handover, and the PDU sessions corresponding to "APP 1" and "APP 2" support inter-access technology handover.

Each URSP rule should include a flow filter and one or more other components that specify how to route the matching flow.

The UE sends a first message to a first AMF entity to indicate the UE to initiate PDU session establishment and whether the PDU session supports switching between access technologies, wherein when the first message carries a first parameter, the PDU session is considered to support switching between the access technologies, and when the first message does not carry the first parameter, the PDU session is considered not to support switching between the access technologies; or, when the first parameter value is 1, the PDU session is considered to support the inter-access technology handover, and when the first parameter value is 0, the PDU session is considered to not support the inter-access technology handover; and vice versa.

For example, the first message may be a NAS message, the NAS message includes a Session ID, a DNN, and first information, the first information may be "N1 SM info", the N1SM information includes PDU Session Establishment Request information (PDU Session Establishment Request), the PDU Session Establishment Request information includes a first parameter, the first parameter may be a Handover Indication (Handover Indication), the Handover Indication is used to indicate that the PDU Session supports Handover between access technologies, for example, the Handover Indication is used to indicate that the PDU Session supports Handover between 3GPP access technologies and non-3GPP access technologies.

The first AMF entity determines a second parameter indicating that the UE is registered in the AMF via one access technology S320.

If the UE is registered on the AMF entity (first AMF entity) through only one access technology, the UE may be registered on the other AMF entity (second AMF entity) through the other access technology. Therefore, after receiving the first message sent by the UE, the first AMF entity needs to determine whether the UE is registered in the first AMF only through one access technology. The first AMF determines the second parameter if the UE is registered in the first AMF only through one access technology. If the UE is registered in the first AMF via another access technology, the second parameter does not need to be determined, for example, the UE is registered in the same AMF via a 3GPP access technology and a non-3GPP access technology.

For example, after receiving the first message sent by the UE, the first AMF entity determines that the UE is registered on the first AMF entity only through the 3GPP access technology or the non-3GPP access technology, and then the first AMF entity determines the second parameter, where the second parameter is a Single AMF entity Indication (Single AMF Indication).

S330, the first AMF entity sends a request for invoking the first service of the SMF entity to the SMF entity, where the request for invoking the first service of the SMF entity includes the first information and the second parameter. Wherein the first service request is for requesting establishment of a PDU session.

After receiving the first message sent by the UE, the first AMF entity needs to select an SMF, and store a correspondence between the session ID and the SMF ID and/or address.

When the UE initiates a PDU session setup, an SMF entity corresponding to the PDU session needs to register, with the UDM entity, a DNN used by the PDU session and an identifier and/or address of the SMF entity. Since the DNN and SMF corresponding to the session ID of the PDU session may or may not change, when the SMF entity registers in the UDM entity, only the changed contents may be updated.

For example, for a UE registered with the same AMF entity through a 3GPP access technology and a non-3GPP access technology, the DNN and SMF used by the UE is unchanged when the PDU session for the UE is handed over from one access technology to another. Whereas for the UE to register in different AMF entities via 3GPP access technology and non-3GPP access technology, the AMF entity is changed.

For the case that the UE is registered in different AMF entities through different access technologies, the UDM further needs to send related information after PDU session establishment to another AMF entity, for example, one or more items of SMF ID and/or address after PDU session establishment, or DNN, and so on.

The first AMF entity may determine that the SMF entity is informed of an access technology registration scenario on which the UE is located. Wherein the first AMF entity may only notify the SMF entity when the UE is registered on it via one of the access technologies, i.e. send the second parameters to the SMF entity,

For example, when the first AMF determines that the UE is registered thereon only through one access technology, the first AMF entity sends an N11 message to the SMF entity, the N11 including the session ID, the DNN, the first information, and the second parameter.

S340, the SMF entity sends a request to the UDM entity for invoking the first service of the UDM entity.

The request for invoking the first service of the UDM entity may further include an access type, where the access type is used to indicate that a UE corresponding to the PDU session managed by the SMF entity is registered in the first AMF entity through a first access technology. The request for invoking the first service of the UDM entity may be used to request registration of a DNN corresponding to the PDU session and information of the SMF entity, where the information of the SMF entity includes an identifier and/or an address of the SMF entity.

After receiving a request for calling a first service of the SMF entity sent by a first AMF entity, the SMF entity allocates an IP address to a PDU session corresponding to the request for calling the first service of the SMF entity, and stores a correspondence between a session ID and the IP address, so that the UE communicates with a User Plane Function (UPF) entity and a data network using the IP address.

The SMF entity further needs to register with the UDM entity, register DNN used by PDU session of the UE and information of the SMF entity, where the information of the SMF entity includes an identifier and/or an address of the SMF entity, and the identifier of the SMF entity may be SMFID.

If the request for invoking the first service of the SMF entity does not include the first information and the second parameter, the SMF entity may consider that the UE corresponding to the PDU session is not registered in another AMF entity, and the SMF entity may not register with the UDM entity, or, during registration, the request for invoking the service of the UDM entity sent to the UDM may not include the DNN.

If the request for invoking the first service of the UDM entity includes the first information and the second parameter, the SMF entity may consider that the UE may be registered with another AMF entity. The request sent by the SMF entity to the UDM to invoke the UDM entity may include the DNN. And S350, the UDM entity determines a second AMF entity registered by the UE by using a second access technology according to the access type, if the second AMF entity exists, the UDM entity calls a second service of the UDM entity and informs the second AMF entity to update the stored subscription data of the UE, wherein the subscription data of the UE comprises the information of the SMF entity and DNN used by PDU session managed by the SMF entity.

If the request for calling the first service of the UDM entity does not include information such as DNN or access type, the UDM entity updates the context of the corresponding UE stored in the UDM according to the request for calling the first service of the UDM entity.

And if the request for calling the first service of the UDM entity comprises information such as DNN or access type, updating the context of the corresponding UE stored by the UDM entity according to the request for calling the first service of the UDM entity. And determining whether a second AMF entity registered by the UE by using a second access technology exists according to the access type, if the second AMF entity exists, calling a second service of the UDM entity by the UDM entity, and informing the second AMF entity to update subscription data of the UE, which is stored by the second AMF entity, wherein the subscription data of the UE comprises the information of the SMF entity and DNN used by PDU session managed by the SMF entity.

S360, the SMF entity sends, to the AMF entity, a response to invoke the first service of the SMF entity, where the response to invoke the first service of the SMF entity includes the second information, and the second information includes a PDU session establishment accept message. For example, the second information may be N1SM information.

S370, the AMF entity sends a second message to the UE, the second message including the second information.

It should be noted that, if the 3GPP access technology and the N3GPP access technology are respectively registered in different PLMNs, the SMF entity in the embodiment is an SMF entity of the HPLMN.

Through the embodiment of the application, the UE may indicate to the AMF entity whether the PDU session requested to be established supports inter-access technology handover, so that when determining that the PDU session supports inter-access technology handover, the AMF entity determines whether to update to the UDM entity according to the registration condition of the UE, or whether to update the DNN during updating. Therefore, the SMF entity updates the information to the UDM entity under not all conditions, or the DNN is not updated under all conditions during updating, so that the signaling resource is saved. In addition, the SMF entity may also determine, according to the indication of the first parameter of the UE, whether the UDM entity needs to update the subscription information of the UE to another AMF entity, so that the UDM entity, in combination with the information sent by the SMF entity, determines that there is another AMF entity registered by the UE through another access technology, and updates the subscription information of the UE to the other AMF entity, thereby saving signaling resources. The SMF updates to the UDM entity after receiving the corresponding indication, or sends DNN to the UDM after receiving the corresponding indication and updating, thereby saving signaling resources. The UDM entity may determine, according to the access type, that the UE is registered in different AMF entities through different access technologies, and update subscription data of the UE to the AMF entities other than the current AMF entity.

Fig. 4 is a schematic signaling interaction diagram of another session establishment method according to an embodiment of the present application. As shown in fig. 3, the method specifically includes the following steps:

s410, the UE sends a first message to the first AMF entity. The first message comprises first information, the first information comprises information requesting to establish the PDU session, and the information requesting to establish the PDU session comprises first parameters. The first message may be an NAS message, the information requesting to establish the PDU session is used to request to the SMF entity to establish the PDU session, and the first parameter is used to instruct the session management function SMF entity to register the data network name DNN used by the PDU session and the identification and/or address of the SMF entity with the user data management UDM entity.

The UE may determine whether the PDU session supports inter-access technology handover based on at least one of user equipment policy or traffic. For details, reference may be made to the related description in the embodiment shown in fig. 3, and details are not repeated here.

After determining that the PDU session supports inter-access technology handover, the UE needs to determine the registration condition of the UE in the first AMF entity.

And when the UE determines that the UE is registered in the first AMF entity through one access technology or the registered AMF entities are different through multiple access technologies, sending a first message carrying the first parameter to the first AMF entity. Among them, the UE may determine the number of AMF entities it registers according to the number of Global User Temporary UE identities (GUTI) it holds. Generally, each time a UE registers with one AMF entity, the AMF entity may allocate one GUTI to the UE. The UE determines that it is registered in the first AMF entity through one access technology when the UE holds one GUTI and is registered in the first AMF entity through only one access technology, or determines that it is registered in the first AMF entity through one access technology when the UE holds multiple GUTIs. For example, the first message may be an NAS message, the NAS message includes a session ID, a DNN, and first information, the first information may be "N1 SM information", the N1SM information includes PDU session Establishment Request information (PDU session Establishment Request), the PDU session Establishment Request information includes a first parameter, the first parameter may be a Handover Indication (Handover Indication), the Handover Indication is used to indicate that the SMF entity registers the data network name DNN used by the PDU session with the user data management UDM entity, and the SMF entity information includes an identifier and/or an address of the SMF entity.

S420, the first AMF entity sends a request for invoking the first service of the SMF entity to the SMF entity, where the request for invoking the first service of the SMF entity includes the first information. Wherein the first service request is for requesting establishment of a PDU session.

After receiving the first message sent by the UE, the AMF entity needs to select an SMF, and store the correspondence between the session ID and the SMF ID and/or address.

When the UE initiates a PDU session setup, an SMF entity corresponding to the PDU session needs to register a Data Network Name (DNN) used by the PDU session and information of the SMF entity with the UDM entity.

For example, a first AMF entity sends a request to an SMF entity to invoke a first service of the SMF entity, the request to invoke the first service of the SMF entity including a session ID, a DNN, and first information.

S430, the SMF entity sends a request for invoking the first service of the UDM entity to the UDM entity, where the request for invoking the first service of the UDM entity includes the information of the SMF entity and the DNN used by the PDU session, and the request for invoking the first service of the UDM entity may further include an access type, where the access type is used to indicate that a UE corresponding to the PDU session managed by the SMF entity is registered in the first AMF entity through the first access technology. The request for invoking the first service of the UDM entity may be for requesting registration of information of the DNN and SMF entities corresponding to the PDU session.

After receiving a request for invoking the first service of the SMF entity sent by the first AMF entity, the SMF entity allocates an IP address to the PDU session corresponding to the request for invoking the first service of the SMF entity, and stores a correspondence between the session ID and the IP address, so that the UE communicates with the UPF entity and the data network using the IP address.

The SMF entity also needs to register with the UDM entity, and register the DNN used by the PDU session of the UE and the information of the SMF entity.

If the request for invoking the first service of the SMF entity does not include the first information, the SMF entity may consider that the terminal corresponding to the PDU session is not registered in another AMF entity, and the SMF entity may not register with the UDM entity, or the request for invoking the UDM entity sent to the UDM may not include the DNN during registration.

If the request for invoking the first service of the SMF entity includes the first information, the SMF entity may consider that the UE may be registered with another AMF entity. The request sent by the SMF entity to the UDM to invoke the UDM entity may include the DNN. And may also include the access type corresponding to the PDU session. And S440, the UDM entity determines a second AMF entity registered by the UE using a second access technology according to the access type, if the second AMF entity exists, the UDM entity calls a second service of the UDM entity and notifies the second AMF entity to update subscription data of the UE stored by the AMF entity, wherein the subscription data of the UE comprises the information of the SMF entity and DNN used by PDU session managed by the SMF entity.

The step S440 can be referred to the description of the step S350 in the embodiment shown in fig. 3, and is not repeated here.

S450, the SMF entity sends, to the AMF entity, a response to invoke the first service of the SMF entity, where the response to invoke the first service of the SMF entity includes the second information, and the second information includes a PDU session setup accept message. For example, the second information may be N1SM information.

S460, the AMF entity sends a second message to the UE, where the second message includes the second information.

By the embodiment of the application, the UE can directly determine whether the PDU session supports switching between access technologies and the registration condition of the UE, and when both meet the conditions, the SMF entity is instructed to register DNN and SMF entity information with the UDM entity. Therefore, the SMF entity updates the information to the UDM entity under not all conditions, or the SMF entity carries DNN when updating to the UDM entity under not all conditions, so that signaling resources are saved. In addition, the SMF entity may also determine, according to the indication of the first parameter of the UE, whether the UDM entity needs to update the subscription information of the UE to another AMF entity, so that the UDM entity, in combination with the information sent by the SMF entity, determines that there is another AMF entity registered by the UE through another access technology, and updates the subscription information of the UE to the other AMF entity, thereby saving signaling resources. The SMF sends information to the UDM entity after receiving the corresponding indication, or updates the DNN after receiving the corresponding indication when the SMF entity updates the UDM entity, thereby saving signaling resources. The UDM entity may determine, according to the access type, that the UE is registered in different AMF entities through different access technologies, and update subscription data of the UE to the AMF entities other than the current AMF entity.

Fig. 5 is a signaling interaction example of a session establishment method according to an embodiment of the present application. As shown in fig. 5, the method specifically includes the following steps:

s501, the UE determines a first parameter, for example, Handover Indication (Handover Indication). Wherein, the UE can determine whether the AMF entity is the same according to the URSP rule and the access technology registration. If the parameter corresponding to the access type in the URSP rule indicates, both access technologies are available, and one of the following two conditions is satisfied: the UE registers with only one access technology, or the UE registers with two access technologies and has two different AMF entities (two Global User temporal IDs, GUTI). Then, when the UE determines that the SMF entity is registered in the UDM entity, the SMF entity needs to update the SMF information and the DNN, and then determines the first parameter.

S502, the UE sends NAS information to the AMF entity, wherein the NAS information comprises session ID, DNN and N1SM information. The N1SM information includes information (PDU Session Establishment Request) requesting to establish a PDU Session, where the information requesting to establish the PDU Session includes a first parameter, and the first parameter is used to indicate that, when an SMF entity is registered with a UDM entity, a data network name DNN used by the PDU Session and an identifier and/or address of the SMF entity are registered with a user data management UDM entity. The NAS message may be included in an RRC message and sent to the RAN entity, and the RAN entity sends the RRC message to the AMF entity, and the RAN may carry an access type (access type) when forwarding.

S503, the AMF entity selects the SMF entity, and stores the corresponding relation between the session ID and the SMF ID and/or the address.

S504, the AMF entity sends, to the SMF entity, a request for invoking the first service of the SMF entity, where the request for invoking the first service of the SMF entity includes the N1SM information received from the UE, and the request for invoking the first service of the SMF entity may further include a session ID, a DNN, and an access type.

S505, the SMF entity obtains UE subscription data from the UDM entity, where the UE subscription data includes DNN and may also include SMF information.

S506, the SMF entity selects a UPF entity according to the DNN and the like, allocates an IP address for the PUD session, stores the corresponding relation between the session ID and the IP address, allocates the tunnel ID and the address for the UPF, sends the tunnel ID and the address to the UPF and establishes the PDU session with the UPF.

S507, the SMF entity sends a response to the AMF entity, where the response to the request to invoke the first service of the SMF entity may include an SM response, where the SM response includes a tunnel ID and an address allocated by the SMF entity to the UPF entity, and PDU session setup accept information (PDU session est.

S508, the AMF entity puts the SM response in the PDU session request and sends the PDU session request to the RAN entity, the RAN entity obtains the tunnel ID and address distributed by the SMF entity for the UPF entity, and the RAN entity sends the uplink data to the UPF entity according to the ID and address.

S509, the RAN entity sends the PDU session establishment accept message to the UE, and establishes a radio bearer of the PDU session.

S510, the RAN entity sends a PDU session request response to the AMF entity, where the PDU session request response includes the tunnel ID and the address allocated by the RAN and the entity.

S511, the AMF entity sends a Request for invoking a second service of the SMF entity to the SMF entity, where the Request for invoking the second service of the SMF entity includes N2 information, and the N2 information carries an SM Request (SM Request with N2Info), where the SM Request includes a tunnel ID and an address allocated by the RAN received from the RAN entity.

S512, the SMF entity modifies the PDU session to the UPF entity, informs the UPF entity of the tunnel ID and address allocated by the RAN entity, and the UPF entity sends downlink data according to the tunnel ID and address allocated by the RAN entity.

S513, the SMF entity replies to the AMF entity a response to the request for invoking the second service of the SMF entity.

S514, the SMF entity determines whether the information of the SMF entity corresponding to the DNN of the PDU session in the UDM entity is itself.

Wherein, it may be determined that the information of the SMF entity corresponding to the DNN of the PDU session in the UDM is not itself according to the UE subscription information obtained in S505.

For example, it is determined whether the information of the SMF entity corresponding to the same DNN in the UE subscription information obtained in S505 is itself according to the DNN included in the request for invoking the SMF first service.

If so, the SMF entity may not register with the UDM entity, or the first service of the UDM entity is invoked, and only the information of the SMF entity corresponding to the DNN is updated to the UDM entity without updating the DNN, wherein the request for invoking the first service of the UDM entity includes the information of the SMF entity.

S515, if the information of the SMF entity corresponding to the DNN in the UE subscription information is not the information of itself, the SMF entity invokes the first service of the UDM entity so as to register as an SMF (register UE Serving SMF) of the UE service in the UDM entity. The contents to be registered include DNN, SMF information, and access type, among others.

S516, the UDM entity determines the access technology used by the PDU session according to the access type, if the corresponding relation between the other access technology and the information of the AMF entity is stored in the context of the UE on the UDM entity, and the information of the AMF entity in the corresponding relation is different from the information of the AMF entity of the access type registered by the current UE, the UDM updates the information and DNN of the SMF entity to the AMF entity corresponding to the information of the AMF entity in the corresponding relation.

Wherein, the information of the SMF entity may include an SMF ID and/or an address; the information of the AMF entity may include an AMF ID and/or an address.

If 3GPP and N3GPP are registered in different PLMNs, respectively, the SMF in the embodiment is the SMF of the HPLMN.

Through the embodiment of the application, the UE may indicate to the AMF entity whether the PDU session requested to be established supports inter-access technology handover, so that when determining that the PDU session supports inter-access technology handover, the AMF entity determines whether to update to the UDM entity according to a registration condition of the UE, or when the SMF entity updates to the UDM entity, determines whether to update the DNN. Therefore, the SMF entity does not update information to the UDM entity under all conditions, or the SMF entity does not update DNN to the UDM entity under all conditions, so that signaling resources are saved. In addition, the SMF entity may also determine, according to the indication of the first parameter of the UE, whether the UDM entity needs to update the subscription information of the UE to another AMF entity, so that the UDM entity, in combination with the information sent by the SMF entity, determines that there is another AMF entity registered by the UE through another access technology, and updates the subscription information of the UE to the other AMF entity, thereby saving signaling resources. The SMF entity updates to the UDM entity after receiving the corresponding indication, or sends DNN to the UDM after the SMF entity updates to the UDM entity after receiving the corresponding indication, thereby saving signaling resources. The UDM entity may determine, according to the access type, that the UE is registered in different AMF entities through different access technologies, and update subscription data of the UE to the AMF entities other than the current AMF entity.

Fig. 6 is a signaling interaction example of another session establishment method provided in the embodiment of the present application. As shown in fig. 6, the method specifically includes the following steps:

s601, the UE determines a first parameter, for example, Handover Indication (Handover Indication). Wherein, the UE judges according to the URSP rule. If the parameter corresponding to the access type in the URSP rule indicates that both access technologies of the PDU session are available, the UE determines that the first parameter needs to be sent to the AMF.

S602, the UE sends a NAS message to the AMF entity, wherein the NAS message comprises session ID, DNN and N1SM information. The N1SM information includes information (PDU Session Establishment Request) requesting to establish a PDU Session, and the information requesting to establish the PDU Session includes a first parameter, and the first parameter is used for the UE to support inter-access technology handover. The NAS message may be included in an RRC message and sent to the RAN entity, and the RAN entity sends the RRC message to the AMF entity, and the RAN may carry an access type (access type) when forwarding.

S603, the AMF entity selects the SMF entity, and stores the corresponding relation between the session ID and the SMF ID and/or the address.

If the AMF entity determines that the UE is registered via one of the access technologies, the AMF entity determines that a second parameter needs to be sent to the SMF.

S604, the AMF entity sends, to the SMF entity, a request to invoke the first service of the SMF entity, where the request to invoke the first service of the SMF entity includes the N1SM information received from the UE, and the request to invoke the first service of the SMF entity may further include the session ID, the DNN, the access type, and the second parameter.

S605, the SMF entity obtains UE subscription data from the UDM entity, where the UE subscription data includes DNN and may also include SMF ID and/or address.

S606, SMF entity selects UPF entity according to DNN, allocates IP address for PUD session, stores the corresponding relation between session ID and IP address, allocates tunnel ID and address for UPF, sends to UPF and establishes PDU session with UPF.

S607, the SMF entity sends a response to the AMF entity to invoke the request of the first service of the SMF entity, where the response to invoke the request of the first service of the SMF entity may include an SM response, where the SM response includes a tunnel ID and an address allocated by the SMF entity to the UPF entity, and a PDU session setup accept message (PDU session est.

S608, the AMF entity puts the SM response in the PDU session request and sends the PDU session request to the RAN entity, the RAN entity obtains the tunnel ID and address allocated by the SMF entity for the UPF entity, and the RAN entity sends the uplink data to the UPF entity according to the ID and address.

S609, the RAN entity sends the received information of the PDU session establishment to the UE and establishes the radio bearer of the PDU session.

S610, the RAN entity sends a PDU session request response to the AMF entity, where the PDU session request response includes the tunnel ID and the address allocated by the RAN and the entity.

S611, the AMF entity sends a Request for invoking the second service of the SMF entity to the SMF entity, where the Request for invoking the second service of the SMF entity includes N2 information, and the N2 information carries an SM Request (SM Request with N2Info), where the SM Request includes a tunnel ID and an address allocated by the RAN received from the RAN entity.

And S612, the SMF entity modifies the PDU session of the UPF entity, informs the UPF entity of the tunnel ID and the address distributed by the RAN entity, and the UPF entity sends downlink data according to the tunnel ID and the address distributed by the RAN entity.

S613, the SMF entity replies to the AMF entity with a response to the request for invoking the second service of the SMF entity.

S614, after receiving the first parameter and the second parameter, the SMF entity determines whether the information of the SMF entity corresponding to the DNN of the PDU session in the UDM entity is self. .

For example, whether the information of the SMF entity corresponding to the same DNN in the UE subscription information is itself is determined according to the DNN included in the request for invoking the SMF first service.

If the SMF entity receives the first parameter and the second parameter, and the DNN included in the request for invoking the SMF first service determines that the information of the SMF entity corresponding to the same DNN in the UE subscription information obtained in S505 is itself, the SMF entity may not register with the UDM entity, or the first service of the UDM entity is invoked, and only the information of the SMF entity corresponding to the DNN is updated to the UDM entity without updating the DNN, where the request for invoking the first service of the UDM entity includes the information of the SMF entity.

S615, if the information of the SMF entity corresponding to the DNN in the UE subscription information is not the information of itself, the SMF entity invokes the second service of the UDM entity so as to register as an SMF (register UE Serving SMF) of the UE service in the UDM entity. The contents to be registered include DNN, SMF information, and access type, among others.

And S616, the UDM entity determines the access technology used by the PDU session according to the access type, and if the corresponding relation between the other access technology and the information of the AMF entity is stored in the context of the UE on the UDM entity, and the information of the AMF entity in the corresponding relation is different from the information of the AMF entity of the access type registered by the current UE, the UDM updates the information and DNN of the SMF entity to the AMF corresponding to the information of the AMF entity in the corresponding relation.

By the embodiment of the application, the UE can directly determine whether the PDU session supports switching between access technologies and the registration condition of the UE, and when both meet the conditions, the SMF entity is instructed to register DNN and SMF entity information with the UDM entity. Therefore, the SMF entity updates the update to the UDM entity under not all conditions, or after receiving the corresponding indication, when the SMF entity updates to the UDM entity, the SMF entity sends DNN to the UDM, and signaling resources are saved. In addition, the SMF entity may also determine, according to the indication of the first parameter of the UE, whether the UDM entity needs to update the subscription information of the UE to another AMF entity, so that the UDM entity, in combination with the information sent by the SMF entity, determines that there is another AMF entity registered by the UE via another access technology, and updates the subscription information of the UE to the another AMF entity, thereby saving signaling resources. The SMF updates to the UDM entity after receiving the corresponding indication, or the SMF entity sends DNN to the UDM when the SMF entity updates to the UDM entity after receiving the corresponding indication, so that signaling resources are saved. The UDM entity may determine, according to the access type, that the UE is registered in different AMF entities through different access technologies, and update subscription data of the UE to the AMF entities other than the current AMF entity.

Fig. 7 is a schematic structural diagram of a UE according to an embodiment of the present application. As shown in fig. 7, the UE may include:

a sending unit 701, configured to send a first message to an AMF entity, where the first message includes first information, the first information includes information requesting to establish a PDU session, and the information requesting to establish the PDU session includes a first parameter, where the first parameter is used to indicate that the PDU session supports handover between different access technologies, or indicate that a session management function SMF entity registers, to the UDM entity, a DNN used by the PDU session and information of the SMF entity;

a receiving unit 702, configured to receive a second message sent by the AMF entity, where the second message includes second information, and the second information includes PDU session establishment acceptance information.

Optionally, the UE further includes:

a determining unit 703 is configured to determine the first parameter according to at least one of a user equipment policy or a service.

Optionally, the determining unit 703 is further configured to determine the first parameter when an access type in the ue policy indicates multiple access technologies, or the ue policy does not include the access type.

Optionally, the sending unit 701 is further configured to send, when the UE is registered by one access technology, or when the AMF entities registered and registered by the UE are different by multiple access technologies, a first message to the AMF entity, where the first message includes first information, the first information includes information requesting to establish a PDU session, and the information requesting to establish the PDU session includes a first parameter, and the first parameter is used to indicate that the SMF entity registers, to the UDM entity, a DNN used by the PDU session and information of the SMF entity.

The UE may be a UE of the session establishment method as described in fig. 3 to 6, and performs the steps performed by the UE in fig. 3 to 6. Therefore, the network equipment can determine the support situation of the PDU session for switching between different access technologies according to the information provided by the UE, even the situation that the UE is registered at the network side, and determine whether to update to the UDM entity, or when the SMF entity updates to the UDM entity, the SMF entity determines whether to update the DNN to the UDM entity. Therefore, the SMF entity updates the information to the UDM entity under not all conditions, or when the SMF entity updates the UDM entity, the SMF entity does not update DNN to the UDM entity under all conditions, and signaling resources are saved.

Fig. 8 is a schematic structural diagram of an AMF entity according to an embodiment of the present application. As shown in fig. 8, the AMF entity may include:

a receiving unit 801, configured to receive a first message sent by a user equipment UE, where the first message includes first information, the first information includes information requesting to establish a protocol data unit PDU session, the information requesting to establish the PDU session includes a first parameter, and the first parameter is used to indicate that the PDU session supports handover between different access technologies, or indicate that a session management function SMF entity registers, to a unified data management UDM entity, a data network name DNN and information of an SMF used by the PDU session;

a sending unit 802, configured to send, to an SMF entity, a request for invoking a first service of the SMF entity, where the request for invoking the first service of the SMF entity includes first information;

the receiving unit 801 is further configured to receive a response, sent by the SMF entity, for invoking the first service of the SMF entity, where the response for invoking the first service of the SMF entity includes second information, and the second information includes PDU session establishment acceptance information;

the sending unit 802 is further configured to send a fourth message to the UE, where the fourth message includes the second information.

Optionally, the AMF entity further includes:

a determining unit 803, configured to determine a second parameter, where the second parameter is used to instruct the UE to register in the AMF through one access technology;

the sending unit 802 is further configured to send, to the SMF entity, a request to invoke the first service of the SMF entity, where the request to invoke the first service of the SMF entity includes the first information and the second parameter.

The AMF entity may be used as the AMF entity of the session establishment method described in fig. 3 to 6, and performs the steps performed by the UE in fig. 3 to 6. Therefore, the SMF entity can determine the support situation of the PDU session for switching between different access technologies according to the information provided by the UE and the AMF entity, even the situation that the UE is registered at the network side, and determine whether to update to the UDM entity, or when the SMF entity updates to the UDM entity, the SMF entity determines whether to update DNN to the UDM entity. Therefore, the SMF entity does not update information to the UDM entity under all conditions, or when the SMF entity updates to the UDM entity, the SMF entity does not update DNN to the UDM entity under all conditions, and signaling resources are saved.

Fig. 9 is a schematic structural diagram of an SMF entity provided in an embodiment of the present application. As shown in fig. 9, the SMF entity may include:

a receiving unit 901, configured to receive a request for invoking a first service of an SMF entity sent by a first access and mobility management function, AMF entity, where the request for invoking the first service of the SMF entity includes first information, the first information includes information requesting to establish a protocol data unit, PDU, session, and the information requesting to establish the PDU session includes a first parameter, and the first parameter indicates that the PDU session supports handover between different access technologies, or indicates that the SMF entity registers, to a user data management, UDM, a data network name, DNN, used by the PDU session and information of the SMF;

a sending unit 902, configured to send, to the first AMF entity, a response to invoke the first service of the SMF entity, where the response to invoke the first service of the SMF entity includes second information, and the second information includes PDU session establishment accept information.

Optionally, when the first parameter indicates that the PDU session supports handover between different access technologies, the request for invoking the first service of the SMF entity further includes a second parameter, where the second parameter is used to indicate that the UE establishing the PDU session is registered in the first AMF through one access technology.

Optionally, the sending unit 902 is further configured to send, to the UDM entity, a request for invoking the first service of the UDM entity, where the request for invoking the first service of the UDM entity includes information of a DNN used by the PDU session and the SMF entity.

The SMF entity may be used as the SMF entity of the session establishment method described in fig. 3 to 6, and performs the steps performed by the UE in fig. 3 to 6. Therefore, the SMF entity can determine the support situation of the PDU session for switching between different access technologies according to the information provided by the UE and the AMF entity, even the situation that the UE is registered at the network side, and determine whether to update to the UDM entity, or when the SMF entity updates to the UDM entity, the SMF entity determines whether to update DNN to the UDM entity. Therefore, the SMF entity does not update information to the UDM entity under all conditions, or when the SMF entity updates to the UDM entity, the SMF entity does not update DNN to the UDM entity under all conditions, and signaling resources are saved.

Fig. 10 is a schematic structural diagram of a UDM entity according to an embodiment of the present application. As shown in fig. 10, the UDM entity includes:

a receiving unit 1001, configured to receive a request for invoking a first service of a UDM entity sent by a session management function, SMF, where the request for invoking the first service of the UDM entity includes an access type, and the access type is used to indicate that a UE corresponding to a PDU session managed by the SMF entity is registered in a first AMF entity through a first access technology;

a determining unit 1002, configured to determine, according to the access type, a second AMF entity that the UE is registered using a second access technology;

a sending unit 1003, configured to invoke a second service of the UDM entity if the second AMF entity exists, notify the second AMF entity to update the stored subscription data of the UE, where the subscription data of the UE includes information of the SMF entity and a DNN used by a PDU session managed by the SMF entity.

The UDM entity may be used as the UDM entity of the session establishment method described in fig. 3 to 6, and performs the steps performed by the UE in fig. 3 to 6. Therefore, the UDM entity can determine the support situation of the PDU session for switching between different access technologies according to the information provided by the UE and the AMF entity, even the situation that the UE is registered at the network side, and determine whether the subscription information of the UE needs to be updated to other AMF entities. Therefore, the UDM does not update the subscription information of the UE with all AMF entities registered to the UE, and signaling resources are saved.

Fig. 11 is a schematic structural diagram of a UE according to an embodiment of the present application. As shown in fig. 11, the UE may include:

a transmitter 1101, configured to send a first message to the AMF entity, where the first message includes first information, the first information includes information requesting to establish a PDU session, and the information requesting to establish the PDU session includes a first parameter, where the first parameter is used to indicate that the PDU session supports handover between different access technologies, or indicate that a session management function, SMF, entity registers, to the UDM entity, information of a DNN and an SMF used by the PDU session;

a receiver 1102, configured to receive a second message sent by the AMF entity, where the second message includes second information, and the second information includes PDU session establishment acceptance information.

Optionally, the UE further includes:

a processor 1103 configured to determine the first parameter according to at least one of a user equipment policy or a service.

Optionally, the processor 1103 is further configured to determine the first parameter when an access type in the ue policy indicates multiple access technologies, or the ue policy does not include the access type.

Optionally, the transmitter 1101 is further configured to, when the UE is registered by one access technology, or the UE is registered by multiple access technologies and the registered AMF entities are different, transmit a first message to the AMF entity, where the first message includes first information, the first information includes information requesting to establish a PDU session, and the information requesting to establish the PDU session includes a first parameter, and the first parameter is used to indicate that the SMF entity registers, with the UDM entity, a DNN used by the PDU session and information of the SMF entity.

In addition, optionally, the UE provided in this embodiment of the present application may further include a memory and a processor 1103. The memory is used for storing corresponding instructions and data so that the processor can call the instructions of the memory to perform corresponding processing on the data.

Fig. 12 is a schematic structural diagram of an AMF entity according to an embodiment of the present application. As shown in fig. 12, the AMF entity may include:

a receiver 1201, configured to receive a first message sent by a user equipment UE, where the first message includes first information, the first information includes information requesting to establish a protocol data unit PDU session, the information requesting to establish the PDU session includes a first parameter, and the first parameter is used to indicate that the PDU session supports handover between different access technologies, or indicate that a session management function SMF entity registers, to a unified data management UDM entity, information of a data network name DNN and an SMF used by the PDU session;

a transmitter 1202, configured to transmit, to an SMF entity, a request to invoke a first service of the SMF entity, where the request to invoke the first service of the SMF entity includes first information;

the receiver 1201 is further configured to receive a response, sent by the SMF entity, for invoking the first service of the SMF entity, where the response for invoking the first service of the SMF entity includes second information, and the second information includes PDU session establishment accept information;

the transmitter 1202 is further configured to transmit a fourth message to the UE, the fourth message including the second information.

Optionally, the AMF entity further includes:

a processor 1203 configured to determine a second parameter, where the second parameter is used for instructing the UE to register in the AMF through one access technology;

the transmitter 1202 is further configured to transmit a request to the SMF entity for invoking the first service of the SMF entity, where the request to invoke the first service of the SMF entity includes the first information and the second parameter.

In addition, optionally, the AMF entity provided in this embodiment may further include a memory and a processor 1203. The memory is used for storing corresponding instructions and data so that the processor can call the instructions of the memory to perform corresponding processing on the data.

Fig. 13 is a schematic structural diagram of an SMF entity provided in an embodiment of the present application. As shown in fig. 13, the SMF entity may include:

a receiver 1301, configured to receive a request for invoking a first service of an SMF entity sent by a first access and mobility management function, AMF, entity, where the request for invoking the first service of the SMF entity includes first information, the first information includes information requesting to establish a protocol data unit, PDU, session, and the information requesting to establish the PDU session includes a first parameter, and the first parameter indicates that the PDU session supports handover between different access technologies, or indicates that the SMF entity registers, to a user data management, UDM, a data network name, DNN, used by the PDU session and information of the SMF;

a transmitter 1302, configured to transmit, to the first AMF entity, a response to invoke the first service of the SMF entity, where the response to invoke the first service of the SMF entity includes second information, and the second information includes PDU session establishment accept information.

Optionally, the transmitter 1302 is further configured to transmit, to the UDM entity, a request to invoke the first service of the UDM entity, where the request to invoke the first service of the UDM entity includes information of the SMF entity and the DNN used by the PDU session.

In addition, optionally, the SMF entity provided in the embodiment of the present application may further include a memory and a processor 1303. The memory is used for storing corresponding instructions and data so that the processor can call the instructions of the memory to perform corresponding processing on the data.

Fig. 14 is a schematic structural diagram of a UDM entity according to an embodiment of the present application. As shown in fig. 14, the UDM entity includes:

a receiver 1401, configured to receive a request for invoking a first service of a UDM entity, where the request for invoking the first service of the UDM entity is sent by a session management function, SMF entity, and the request for invoking the first service of the UDM entity includes an access type, where the access type is used to indicate that a UE corresponding to a PDU session managed by the SMF entity is registered in a first AMF entity through a first access technology;

a processor 1402 for determining a second AMF entity for the UE to register with a second access technology according to the access type;

a transmitter 1403, configured to invoke the second service of the UDM entity and notify the second AMF entity to update the saved subscription data of the UE if the second AMF entity exists, where the subscription data of the UE includes an identifier and/or an address of the SMF entity and a DNN used by the PDU session managed by the SMF entity.

The present application provides a computer program product containing instructions for performing the above-described methods/steps of fig. 3 to 6 when the instructions are run on a computer.

The present application provides a computer-readable storage medium for storing instructions, which when executed on a computer, perform the methods/steps of fig. 3 to 6 described above.

In the various embodiments of the invention described above, implementation may be in whole or in part via software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk), among others.

The above description is only for the preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A session establishment method, comprising:

the method comprises the steps that User Equipment (UE) determines a first parameter according to at least one of user equipment strategies or services; wherein, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not define the access type, the UE determines the first parameter, and the user equipment policy is a user equipment routing policy, URSP;

user Equipment (UE) sends a first message to an access and mobility management function (AMF) entity, wherein the first message comprises first information, the first information comprises information for requesting to establish a Protocol Data Unit (PDU) session, the information for requesting to establish the PDU session comprises a first parameter, and the first parameter is used for indicating the SMF entity to register a Data Network Name (DNN) used by the PDU session and the information of the SMF entity to a Unified Data Management (UDM) entity;

and the UE receives a second message sent by the AMF entity, wherein the second message comprises second information, and the second information comprises the PDU session establishment acceptance information.

2. The method of claim 1, wherein the UE sends a first message to an AMF entity, the first message including first information, the first information including information requesting establishment of a PDU session, the information requesting establishment of the PDU session including a first parameter, and the first parameter is used to indicate that an SMF entity registers, with a UDM entity, a DNN used by the PDU session and the information of the SMF entity, and specifically includes:

when the UE is registered by one access technology or the UE is registered by multiple access technologies and the registered AMF entities are different, the UE sends a first message to the AMF entity, wherein the first message comprises first information, the first information comprises information requesting to establish a PDU session, and the information requesting to establish the PDU session comprises a first parameter, and the first parameter is used for indicating that the SMF entity registers DNN used by the PDU session and the information of the SMF entity with the UDM entity.

3. A session establishment method, comprising:

an access and mobility management function (AMF) entity receives a first message sent by User Equipment (UE), wherein the first message comprises first information, the first information comprises information requesting to establish a Protocol Data Unit (PDU) session, the information requesting to establish the PDU session comprises a first parameter, the first parameter is used for indicating the Session Management Function (SMF) entity to register a Data Network Name (DNN) used by the PDU session and the information of the SMF to a Unified Data Management (UDM) entity, and the first parameter is determined by at least one of user equipment policy or service before the UE sends the first message to the AMF entity; wherein, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not define the access type, the UE determines the first parameter, and the user equipment policy is a user equipment routing policy, URSP;

the AMF entity sends a request for calling a first service of the SMF entity to the SMF entity, wherein the request for calling the first service of the SMF entity comprises the first information;

the AMF entity receives a response which is sent by the SMF entity and used for calling the first service of the SMF entity, wherein the response which is used for calling the first service of the SMF entity comprises second information, and the second information comprises PDU session establishment acceptance information;

the AMF entity sends a fourth message to the UE, wherein the fourth message comprises the second information.

4. A session establishment method, comprising:

a Session Management Function (SMF) entity receives a request for invoking a first service of the SMF entity, wherein the request for invoking the first service of the SMF entity is sent by a first access and mobility management function (AMF) entity and comprises first information, the first information comprises information for requesting to establish a Protocol Data Unit (PDU) session, the information for requesting to establish the PDU session comprises a first parameter, the first parameter indicates a Data Network Name (DNN) used by the PDU session and the information of the SMF to be registered by the SMF entity to a User Data Management (UDM) entity, and the first parameter is determined by at least one of user equipment policy or service before a User Equipment (UE) sends a first message to the AMF entity; wherein, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not define the access type, the UE determines the first parameter, and the user equipment policy is a user equipment routing policy, URSP;

the SMF entity sends a response for calling the first service of the SMF entity to the first AMF entity, wherein the response for calling the first service of the SMF entity comprises second information, and the second information comprises PDU session establishment acceptance information.

5. The method of claim 4, wherein the request to invoke the first service of the SMF entity further comprises a second parameter indicating that the UE establishing the PDU session is registered with the first AMF via one access technology when the first parameter indicates that the PDU session supports handover between different access technologies.

6. The method of claim 4 or 5, further comprising:

and the SMF entity sends a request for calling the first service of the UDM entity to the UDM entity, wherein the request for calling the first service of the UDM entity comprises the DNN used by the PDU session and the information of the SMF entity.

7. A User Equipment (UE), comprising:

a processor configured to determine a first parameter based on at least one of a user equipment policy or a service; wherein, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not define the access type, the first parameter is determined, and the user equipment policy is a user equipment routing policy URSP;

a transmitter, configured to send a first message to an access and mobility management function (AMF) entity, where the first message includes first information, where the first information includes information requesting establishment of a Protocol Data Unit (PDU) session, and the information requesting establishment of the PDU session includes a first parameter, where the first parameter is used to indicate that the PDU session supports handover between different access technologies, or indicate that a Session Management Function (SMF) entity registers, with a Unified Data Management (UDM) entity, a Data Network Name (DNN) used by the PDU session and information of the SMF entity;

a receiver, configured to receive a second message sent by the AMF entity, where the second message includes second information, and the second information includes information of PDU session establishment acceptance.

8. The UE of claim 7, wherein the transmitter is further configured to transmit a first message to the AMF entity when the UE is registered with one access technology or the UE is registered with multiple access technologies and the registered AMF entities are different, wherein the first message includes first information, the first information includes information requesting establishment of a PDU session, the information requesting establishment of a PDU session includes a first parameter, and the first parameter is used to indicate that the SMF entity registers DNN used by the PDU session with the UDM entity and the information of the SMF entity.

9. An access and mobility management function, AMF, entity, comprising:

a receiver, configured to receive a first message sent by a user equipment UE, where the first message includes first information, where the first information includes information requesting to establish a protocol data unit, PDU, session, and the information requesting to establish the PDU session includes a first parameter, where the first parameter is used to indicate that the PDU session supports handover between different access technologies, or indicate that a session management function, SMF, entity registers, with a unified data management, UDM, entity, a data network name, DNN, used by the PDU session and information of the SMF, and the first parameter is determined according to at least one of a user equipment policy or a service before the UE sends the first message to the AMF entity; wherein, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not define the access type, the UE determines the first parameter, and the user equipment policy is a user equipment routing policy, URSP;

a transmitter, configured to transmit, to an SMF entity, a request to invoke a first service of the SMF entity, where the request to invoke the first service of the SMF entity includes the first information;

the receiver is further configured to receive a response, sent by the SMF entity, to invoke the first service of the SMF entity, where the response to invoke the first service of the SMF entity includes second information, and the second information includes PDU session establishment accept information;

the transmitter is further configured to transmit a fourth message to the UE, the fourth message including the second information.

10. The AMF entity of claim 9, further comprising:

a processor configured to determine a second parameter indicating that the UE is registered with the AMF via one access technology;

the transmitter is further configured to transmit the request for invoking the first service of the SMF entity to the SMF entity, where the request for invoking the first service of the SMF entity includes the first information and the second parameter.

11. A session management function, SMF, entity, comprising:

a receiver, configured to receive a request for invoking a first service of an SMF entity sent by an AMF entity, where the request for invoking the first service of the SMF entity includes first information, the first information includes information requesting to establish a PDU session, and the information requesting to establish the PDU session includes a first parameter, where the first parameter indicates that the PDU session supports handover between different access technologies, or indicates that the SMF entity registers, with an UDM entity, a data network name DNN used by the PDU session and information of the SMF, and the first parameter is determined according to at least one of a UE policy or a service before a UE sends a first message to the AMF entity; wherein, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not define the access type, the UE determines the first parameter, and the user equipment policy is a user equipment routing policy, URSP;

a transmitter, configured to transmit, to the first AMF entity, a response to invoke the first service of the SMF entity, where the response to invoke the first service of the SMF entity includes second information, and the second information includes PDU session establishment accept information.

12. The SMF entity of claim 11, wherein the request to invoke the first service of the SMF entity further comprises a second parameter indicating that the UE establishing the PDU session is registered with the first AMF via one access technology when the first parameter indicates that the PDU session supports handover between different access technologies.

13. The SMF entity according to claim 11 or 12, wherein said transmitter is further configured to send a request to a UDM entity to invoke the first service of said UDM entity, said request to invoke the first service of said UDM entity comprising the DNN used by said PDU session and the address and/or identity of said SMF entity.

14. A User Equipment (UE), comprising:

a determining unit, configured to determine a first parameter according to at least one of a user equipment policy or a service; wherein, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not define the access type, the first parameter is determined, and the user equipment policy is a user equipment routing policy URSP;

a sending unit, configured to send a first message to an access and mobility management function (AMF) entity, where the first message includes first information, where the first information includes information requesting establishment of a Protocol Data Unit (PDU) session, and the information requesting establishment of the PDU session includes a first parameter, where the first parameter is used to indicate that the PDU session supports handover between different access technologies, or indicate that a Session Management Function (SMF) entity registers, to a Unified Data Management (UDM) entity, a Data Network Name (DNN) used by the PDU session and information of the SMF entity;

a receiving unit, configured to receive a second message sent by the AMF entity, where the second message includes second information, and the second information includes information of PDU session establishment acceptance.

15. The UE of claim 14, wherein the sending unit is further configured to send a first message to the AMF entity when the UE is registered with one access technology or the UE is registered with multiple access technologies and the registered AMF entities are different, where the first message includes first information, the first information includes information requesting establishment of a PDU session, and the information requesting establishment of a PDU session includes a first parameter, and the first parameter is used to indicate that the SMF entity registers, with the UDM entity, DNN used by the PDU session and the information of the SMF entity.

16. An access and mobility management function, AMF, entity, comprising:

a receiving unit, configured to receive a first message sent by a user equipment UE, where the first message includes first information, where the first information includes information requesting to establish a protocol data unit, PDU, session, and the information requesting to establish the PDU session includes a first parameter, where the first parameter is used to indicate that the PDU session supports handover between different access technologies, or indicate that a session management function, SMF, entity registers, to a unified data management, UDM, entity, a data network name, DNN, used by the PDU session and information of the SMF, and the first parameter is determined according to at least one of a user equipment policy and a service before the UE sends the first message to the AMF entity; wherein, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not define the access type, the UE determines the first parameter, and the user equipment policy is a user equipment routing policy, URSP;

a sending unit, configured to send, to an SMF entity, a request to invoke a first service of the SMF entity, where the request to invoke the first service of the SMF entity includes the first information;

the receiving unit is further configured to receive a response, sent by the SMF entity, to invoke the first service of the SMF entity, where the response to invoke the first service of the SMF entity includes second information, and the second information includes information for PDU session establishment acceptance;

the sending unit is further configured to send a fourth message to the UE, where the fourth message includes the second information.

17. The AMF entity of claim 16, further comprising:

a determining unit, configured to determine a second parameter, where the second parameter is used to instruct the UE to register in the AMF through one access technology;

the sending unit is further configured to send, to the SMF entity, the request for invoking the first service of the SMF entity, where the request for invoking the first service of the SMF entity includes the first information and the second parameter.

18. A session management function, SMF, entity, comprising:

a receiving unit, configured to receive a request for invoking a first service of an SMF entity, where the request for invoking the first service of the SMF entity is sent by an AMF entity, where the request for invoking the first service of the SMF entity includes first information, the first information includes information requesting to establish a PDU session, and the information requesting to establish the PDU session includes a first parameter, where the first parameter indicates that the PDU session supports handover between different access technologies, or indicates that the SMF entity registers, to a UDM entity, a data network name DNN used by the PDU session and information of the SMF, and the first parameter is determined according to at least one of a user equipment policy or a service before a UE sends a first message to the AMF entity; wherein, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not define the access type, the UE determines the first parameter, and the user equipment policy is a user equipment routing policy, URSP;

a sending unit, configured to send, to the first AMF entity, a response to invoke the first service of the SMF entity, where the response to invoke the first service of the SMF entity includes second information, and the second information includes information for PDU session establishment acceptance.

19. The SMF entity of claim 18, wherein the request to invoke the first service of the SMF entity further comprises a second parameter indicating that the UE establishing the PDU session is registered with the first AMF via one access technology when the first parameter indicates that the PDU session supports handover between different access technologies.

20. The SMF entity according to claim 18 or 19, wherein said sending unit is further configured to send a request for invoking the first service of the UDM entity to the UDM entity, and wherein the request for invoking the first service of the UDM entity comprises the DNN used by the PDU session and the address and/or identity of the SMF entity.

21. A computer readable storage medium comprising computer readable instructions which, when read and executed by a computer, cause the computer to perform the method of any one of claims 1 to 6.