WO2019033269A1 - Method and device for establishing session - Google Patents

Abstract

Embodiments of the present application relate to a method and a device for establishing a session. The method specifically comprises: UE indicating to an AMF entity whether a PDU session that the AMF entity requests to establish supports switching between access technologies, such that upon determining that the PDU session supports switching between access technologies, the AMF entity determines, according to a registration status of the UE, whether a DNN needs to be updated with a UDM entity; alternatively, the UE directly determining whether the PDU session supports switching between access technologies and the registration status of the UE, and when both meet conditions, instructing an SMF entity to register information of the DNN and the SMF entity with the UDM entity. Thereby, the SMF entity does not update the DNN with the UDM entity in all scenarios, reducing signaling resources.

Description

Method and device for establishing session Technical field

The embodiments of the present invention relate to the field of communications technologies, and in particular, to a method and a device for establishing a session.

Background technique

In a 5G network, user equipment (UE) can be registered in the core network through the third generation partnership project (3GPP) access technology and the Non-3GPP access technology. For example, the Non-3GPP access technology may be a wireless local area networks (WLAN) technology. When registering, the access and mobility management function (AMF) updates the currently registered AMF ID and address to the unified data management (UDM) entity, and each access technology is stored on the UDM entity. The AMF ID and/or address corresponding to the access technology type (AT type).

When the UE needs to use the service, a protocol data unit (PDU) session is established through the corresponding access technology. And, the UE may choose to switch the PDU session that has been established through one access technology to another access technology.

When the PDU session is switched, the UDM entity notifies the UE of the registered AMF entity, 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 during the PDU session handover. When the information corresponding to the PDU session is updated, all AMFs registered by the access technology are notified. Entity, but the AMF entity registered by the access technology used by the current PDU session does not need to be updated, wasting signaling.

Summary of the invention

The embodiment of the present application provides a session establishment method and device. To achieve less signaling resources during session establishment.

In a first aspect, an embodiment of the present application provides a session establishment method. The method includes: the UE sends a first message to the AMF entity, for example, the first message may be a Non-Access Stratum (NAS) message; the first message includes first information, for example, the first information may be N1 session management (SM) information; the first information includes information for requesting to establish a PDU session, where the information of the request to establish a PDU session includes a first parameter, for example, the first parameter may be a handover indication; the first parameter It is used to indicate that the PDU session supports handover between different access technologies, for example, support switching between 3GPP access technology and non-3GPP access technology. Alternatively, the first parameter is used to indicate that the SMF entity registers the data network name (DNN) used by the PDU session with the UMF entity and the information of the SMF entity, wherein the information of the SMF entity includes the identifier and/or address of the SMF entity. The UE receives the second message sent by the AMF entity, where the second message includes the second information, for example, the second information may be N1SM information, and the second information includes information that the PDU session establishment accepts. Through the embodiment of the present application, the UE can be directed to the AMF. Indicates whether the PDU session that the request establishes supports inter-access technology handover, so that when the AMF entity determines that the PDU session supports handover between access technologies, it is determined whether the DNN needs to be updated to the UDM entity according to the registration status of the UE. Alternatively, the UE may directly determine whether the PDU session supports handover between access technologies and the registration status of the UE, and when both meet the condition, instruct the SMF entity to register the information of the DNN and the SMF entity with the UDM entity. Therefore, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM entity, not all cases update the DNN corresponding to the UE, saving signaling resources. 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 other AMF entities, so that the UDM entity combines the information sent by the SMF entity to determine that the UE is registered by other access technologies. When other AMF entities are used, the subscription information of the UE is updated to other AMF entities.

In an optional implementation, before the UE sends the first message to the AMF entity, the method further includes: determining, by the UE, the first parameter according to at least one of a user equipment policy or a service. With the embodiment of the present application, the UE may determine whether a PDU session supports handover between access technologies according to an access type in the user equipment policy, or determine a PDU session corresponding to the service flow according to a specific service flow, such as a service flow identifier. Whether to support switching between different access technologies.

In another optional implementation, when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not limit the access type, the UE determines the first parameter. For example, when the 3GPP access technology and the non-3GPP access technology are indicated in the access type in the user equipment policy, the UE determines a first parameter, where the first parameter is used to indicate that the PDU session supports the 3GPP access technology and the non-3GPP access. Switch between technologies. The embodiment of the present application may be implemented to determine whether a PDU session supports switching between access technologies according to an access type in a user equipment policy.

In another optional implementation, the UE sends a first message to the AMF entity, where the foregoing first message includes first information, where the first information includes information requesting to establish a PDU session, and the information of the request to establish a PDU session includes a first parameter. The first parameter is used to indicate that the SMF entity registers the DNN and the identifier and/or address of the SMF entity used by the PDU session with the UMM entity, and specifically includes: when the UE registers through an access technology, or the UE accesses through multiple accesses. When the technology is registered and the registered AMF entity is different, the UE sends a first message to the AMF entity, where the first message includes first information, where the first information includes information for requesting to establish a PDU session, and the information of the request to establish a PDU session includes the first a parameter, the first parameter is used to instruct the SMF entity to register the DNN and the SMF entity information used by the PDU session with the UDM entity. With the embodiment of the present application, when the UE determines that it is registered by an access technology, or is registered by multiple access technologies and is registered in different AMF entities, the UE sends the first parameter carrying the first parameter to the AMF entity. In one message, signaling resources are less occupied.

With the embodiment of the present application, the UE may indicate to the AMF entity whether the PDU session that it requests to establish supports the handover between access technologies, so that when the AMF entity determines that the PDU session supports the handover between access technologies, it is determined according to the registration status of the UE. Whether you need to update the DNN to the UDM entity. Alternatively, the UE may directly determine whether the PDU session supports handover between access technologies and the registration status of the UE, and when both meet the condition, instruct the SMF entity to register the information of the DNN and the SMF entity with the UDM entity. Thus, the SMF entity does not update the information to the UDM entity in all cases, or the SMF entity updates the DNN in all cases when updating to the UDM entity, saving signaling resources. 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 other AMF entities, so that the UDM entity combines the information sent by the SMF entity to determine that the UE is registered by other access technologies. When other AMF entities, the UE's subscription information is updated to other AMF entities, thereby saving signaling resources.

In a second aspect, an embodiment of the present application provides a session establishment method. The method includes: the AMF entity receives the first message sent by the UE, where the first message includes the first information, where the first information includes information for requesting to establish a PDU session, where the information of the request to establish the PDU session includes a first parameter, where the first parameter is used. Instructing the PDU session to support handover between different access technologies, or instructing the SMF entity to register the DNN used by the PDU session with the information of the SMF, wherein the information of the SMF entity includes the identifier and/or address of the SMF entity; The entity sends a request to the SMF entity to invoke the first service of the SMF entity, the request to invoke the first service of the SMF entity includes first information; the AMF entity receives a response sent by the SMF entity to invoke the first service of the SMF entity, the call The response of the first service of the SMF entity includes second information including a PDU session establishment accept message; the AMF entity sends a fourth message to the UE, the fourth message including the second information. With the embodiment of the present application, when the AMF entity receives the handover between the PDU session and the access technology that the UE requests to establish, the AMF entity determines whether the DNN needs to be updated to the UDM entity according to the registration status of the UE. Alternatively, the UE may directly determine whether the PDU session supports handover between access technologies and the registration status of the UE. When both of the conditions are met, the AMF instructs the SMF entity to register the information of the DNN and the SMF entity with the UDM entity. Thus, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM entity, not all cases update the DNN, and the UE is not sent in all cases. NAS messages carry the first parameter and save signaling resources.

In an optional implementation, the AMF entity receives the first message sent by the UE, where the first message includes first information, where the first information includes information requesting to establish a PDU session, where the information of the request to establish a PDU session includes the first message. a parameter, the first parameter is used to indicate that the PDU session supports the handover between different access technologies, and the method further includes: the AMF entity determining the second parameter, where the second parameter is used to indicate that the UE is registered by using an access technology Said AMF. At this time, the AMF entity sends a request to the SMF entity to invoke the first service of the SMF entity, where the request for the first service of the SMF entity includes the first information, and specifically includes: the AMF entity sends a call to the SMF entity to invoke the SMF entity. A request for a service, the request to invoke the first service of the SMF entity includes a first information and a second parameter. With the embodiment of the present application, when the AMF entity receives the first message sent by the UE, the AMF determines the registration status of the UE, and when it is determined that the UE is registered on the AMF by using an access technology, the first parameter is sent to the SMF entity. The second parameter is a request to invoke the first service of the SMF entity. In other cases, the request to the SMF entity to invoke the first service of the SMF entity does not need to carry the second parameter, thereby saving signaling.

With the embodiment of the present application, when the AMF entity receives the handover between the PDU session and the access technology that the UE requests to establish, the AMF entity determines whether the DNN needs to be updated to the UDM entity according to the registration status of the UE. Alternatively, the UE may directly determine whether the PDU session supports handover between access technologies and the registration status of the UE. When both of the conditions are met, the AMF instructs the SMF entity to register the information of the DNN and the SMF entity with the UDM entity. Therefore, the SMF entity does not update the DNN to the UDM entity in all cases, and the UE does not carry the first parameter in all cases, thereby saving signaling resources.

In a third aspect, an embodiment of the present application provides a session establishment method. The method includes: the SMF entity receives a request sent by the AMF entity to invoke the first service of the SMF entity, where the request for the first service of the SMF entity includes the first information, where the first information includes information requesting to establish a PDU session, and the request establishes a PDU. The session information includes a first parameter indicating that the PDU session supports handover between different access technologies, or instructing the SMF entity to register the DNN and the SMF information used by the PDU session to the UDM entity, wherein the information of the SMF entity includes the SMF. An identifier and/or an address of the entity; the SMF entity sends a response to the first AMF entity to invoke the first service of the SMF entity, and the response of the first service that invokes the SMF entity includes the second information, where the second information includes the PDU session establishment acceptance information. The SMF entity sends the information to the UDM entity after receiving the corresponding indication by the embodiment of the present application, or updates the DNN when the SMF entity updates to the UDM entity after receiving the corresponding indication, thereby saving signaling resources.

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, where the second parameter is used to indicate establishment. The UE of the PDU session is registered in the first AMF by an access technology. With the embodiment of the present application, the SMF determines that the UE supports handover between different access technologies, and the current AMF entity is registered by only one access technology. At this time, the SMF entity updates the subscription information of the UE to the UDM entity. The subscription information of the UE includes a DNN.

In another optional implementation, the method further includes: the SMF entity sending a request to the UDM entity to invoke the first service of the UDM entity, where the request for the first service of the UDM entity includes information about the DNN used by the PDU session and the SMF entity.

With the embodiment of the present application, the SMF does not update the UDM entity after receiving the corresponding indication, or after receiving the corresponding indication, the SMF entity sends the DNN to the UDM entity, which saves signaling resources.

In a fourth aspect, an embodiment of the present application provides a session establishment method. The method includes: the UDM entity receives a request sent by the SMF entity to invoke the first service of the UDM entity, where the request for the first service of the UDM entity includes an access type, where the access type is used to indicate that the PDU session managed by the SMF entity corresponds to The UE is registered by the first AMF entity by using the first access technology; the UDM entity determines, according to the access type, the second AMF entity that the UE registers with the second access technology, and if the second AMF entity exists, the UDM entity invokes the UDM entity. a second service, notifying the second AMF entity to update the subscription data of the saved UE, where the subscription data of the UE includes information of the SMF entity and a DNN used by the MF session managed by the SMF entity, where the information of the SMF entity includes the SMF The identity and/or address of the entity.

With the embodiment of the present application, the UDM entity may determine, according to the access type, that when the UE registers with different AMF entities through different access technologies, the UDM entity may update the subscription data of the UE to the AMF entity other than the current AMF entity.

In a fifth aspect, a UE is provided having functionality to implement UE behavior in the first aspect described above and its alternative implementation. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. With the embodiment of the present application, the UE may indicate to the AMF entity whether the PDU session that it is requesting to establish supports the handover between access technologies, so that the AMF entity determines, according to the registration status of the UE, when determining the handover between the PDU sessions and the access technologies. Whether you need to update the DNN to the UDM entity. Alternatively, the UE may directly determine whether the PDU session supports handover between access technologies and the registration status of the UE. When both of the conditions are met, the SMF entity is instructed to register the information of the DNN and the SMF entity with the UMM entity, where the SMF entity The information includes the identity and/or address of the SMF entity. Thus, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM entity, not all cases update the DNN, saving signaling resources. 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 other AMF entities, so that the UDM entity combines the information sent by the SMF entity to determine that the UE is registered by other access technologies. When other AMF entities, the UE's subscription information is updated to other AMF entities, thereby saving signaling resources.

In a sixth aspect, there is provided an AMF entity having the functionality to implement the AMF entity behavior in the second aspect above and its alternative implementation. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. Implemented by this application For example, when the AMF entity receives the handover between the PDU session and the access technology indicated by the UE, the AMF entity determines whether it is necessary to update the DNN to the UDM entity according to the registration status of the UE. Alternatively, the UE may directly determine whether the PDU session supports handover between access technologies and the registration status of the UE. When both of the conditions are met, the AMF instructs the SMF entity to register the information of the DNN and the SMF entity with the UDM entity. Therefore, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM, not all cases update the DNN, and the UE is not in all cases, the NAS is sent. The messages carry the first parameter and save signaling resources.

In a seventh aspect, there is provided an SMF entity having the functionality to implement the SMF entity behavior in the third aspect above and its alternative implementation. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. With the embodiment of the present application, the SMF sends the DNN to the UDM entity after receiving the corresponding indication, which saves signaling resources.

In an eighth aspect, a UDM entity is provided having the functionality to implement the UDM entity behavior in the third aspect above and its alternative implementations. The functions may be implemented by hardware or by corresponding software implemented by hardware. The hardware or software includes one or more modules corresponding to the functions described above. With the embodiment of the present application, the UDM entity may determine, according to the access type, that when the UE registers with different AMF entities through different access technologies, the UDM entity may update the subscription data of the UE to the AMF entity other than the current AMF entity.

According to a ninth aspect, there is provided a computer readable storage medium having stored thereon a computer program, the computer program being executed by a processor to implement the first aspect, the second aspect, the third aspect, and the fourth aspect A method as described in any one or more of the aspects.

According to a tenth aspect, there is provided a computer program product comprising instructions for causing a computer to perform any one or more of the first, second, third and fourth aspects described above when the instructions are run on a computer The method described in the aspects.

With the embodiment of the present application, the UE may indicate to the AMF entity whether the PDU session that it requests to establish supports the handover between access technologies, so that when the AMF entity determines that the PDU session supports the handover between access technologies, it is determined according to the registration status of the UE. Whether to update the information to the UDM entity, or when the SMF entity updates to the UDM entity, determine whether the DNN needs to be updated. Alternatively, the UE may directly determine whether the PDU session supports handover between access technologies and the registration status of the UE, and when both meet the condition, instruct the SMF entity to register the information of the DNN and the SMF entity with the UDM entity. Thus, the SMF entity does not update the information to the UDM entity in all cases, or, when the SMF entity updates to the UDM entity, not all cases update the DNN, saving signaling resources. 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 other AMF entities, so that the UDM entity combines the information sent by the SMF entity to determine that the UE is registered by other access technologies. When other AMF entities, the UE's subscription information is updated to other AMF entities, thereby saving signaling resources. The SMF sends the DNN to the UDM entity after receiving the corresponding indication, saving signaling resources. The UDM entity may determine, according to the access type, that when the UE registers with different AMF entities through different access technologies, the UDM entity may update the subscription data of the UE to the AMF entity 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 application;

2 is a schematic structural diagram of another 5G communication network according to an embodiment of the present application;

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

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

FIG. 5 is a schematic diagram of signaling interaction of a session establishment method according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of signaling interaction of another session establishing method according to an embodiment of the present disclosure;

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

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

FIG. 9 is a schematic structural diagram of an SMF entity according to an embodiment of the present disclosure;

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 according to an embodiment of the present disclosure;

FIG. 12 is a schematic structural diagram of another AMF entity according to an embodiment of the present disclosure;

FIG. 13 is a schematic structural diagram of another SMF entity according to an embodiment of the present disclosure;

FIG. 14 is a schematic structural diagram of another UDM entity provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application.

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

In the embodiment of the present application, the user equipment may also be referred to as a terminal, which may be a device that provides voice and/or data connectivity to the user, a handheld device with a wireless connection function, or other processing connected to the wireless modem. device. The wireless terminal can communicate with one or more core networks via the RAN, which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device, for example, can be portable, pocket-sized , handheld, computer built-in or in-vehicle mobile devices that exchange language and/or data with a wireless access network. For example, personal communication service (PCS) telephone, cordless telephone, session initiated protocol (SIP) telephone, wireless local loop (WLL) station, personal digital assistant (personal digital assistant, PDA) and other equipment. A wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, an access point, The remote terminal, the access terminal, the user terminal, the user agent, the user device, or the user equipment are in the embodiment of the present application. Not limited. According to the service type, the UE involved in the embodiment of the present invention may be a terminal device with high requirements for speed and mobility, such as a mobile phone, a multimedia device, or the like, or an Internet of Things terminal, or a car network. Terminal.

A network slice is implemented into a network deployment instance (network slice instance (NSI)). A network slice can 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 according to an embodiment of the present application.

As shown in FIG. 1 and FIG. 2, in the embodiment of the present application, the AMF entity, the SMF entity, the UDM entity, and the user plane function (UPF) entity may be one or more servers in the core network of the 5G communication network. . The UE may communicate with the core network of the 5G communication network through a 3GPP access technology or a non-3GPP access technology. For example, the UE may access the 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 pass the Wireless Fidelity (Wireless-Fidelity, The Wi-Fi technology and the non-3GPP inter-working function (N3IWF) entity access the core network of the 5G communication network for communication. The eNB accesses through the evolved universal terrestrial radio access (E-UTRA) technology, or through the RAN through the new radio (NR), which can be considered as being connected through the 3GPP. Incoming technology access; access through Wi-Fi technology can be considered to be accessed through non-3GPP access technology.

The function of each module in the 5G communication network is briefly introduced below.

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

SMF entities have functions such as session management and roaming. Among them, session management functions, for example, session establishment, modification, and release, include tunnel maintenance of UPF and access network (AN) nodes. The roaming function may include charging data collection, and signaling transmission supporting authentication/authorization with an external data network (DN).

The UPF entity has functions such as packet routing and lawful interception.

UDM entities have the functions of authentication certificate processing, user identification processing, access authorization, registration and mobility management, subscription management, and SMS management.

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

The UE and the RAN are connected through the Uu interface; the signaling and data between the RAN device and the AMF entity pass through the N2 interface; the signaling and data between the AMF entity and the SMF entity are transmitted through the N11 interface; and the letter between the SMF entity and the UPF entity Let the data be 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 can be specifically referred to the 3GPP standard.

As shown in FIG. 1 , when the UE registers 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 registers in the 5G network, it may also be registered in different AMF entities through the 3GPP access technology and the non-3GPP access technology. 2, 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 registers in the 5G network, it can also register with the AMF entity through only the 3GPP access technology or the non-3GPP access technology.

The PDU session of the UE needs to be switched from one access technology to another when the UE registers with the same AMF entity through the 3GPP access technology and the non-3GPP access technology.

In order to ensure service continuity, when the PDU session is switched to another access technology, the IP address used by the PDU session needs to be guaranteed. In order to achieve this, when the UE initiates a handover of the PDU session to the AMF entity, the AMF entity needs to select the SMF entity used before the PDU session. Since the IP address of the PDU session is stored on the SMF entity, selecting the same SMF entity can ensure that the IP address of the PDU session does not change.

For example, when the UE establishes a PDU session on the 3GPP, the AMF entity saves the correspondence between the session ID and the SMF ID and/or the address, and the SMF entity saves the correspondence between the session ID and the IP address. When the UE initiates a PDU session handover on the non-3GPP, that is, the PDU session is reestablished, the UE carries the same session ID. Because the AMF entities are the same, Then, the AMF entity can find the same SMF according to the correspondence between the saved session ID and the SMF ID and/or address. After receiving the PDU session establishment request, the SMF uses the same IP address for the UE according to the correspondence between the session ID and the IP address maintained in the SMF.

For example, when the UE registers different AMFs by using two access technologies, because the AMF entity registered by the 3GPP access technology and the N3GPP technology is different, when the PDU session is switched, the AMF entity includes the UE subscription data notified by the UDM. SMF ID/Address, select the same SMF.

The PDU session establishment (reconstruction) method is further introduced by the UE in the case that the UE is registered by only one access technology or the UE is registered by multiple access technologies but the registered AMF entities are different.

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

S310. The UE sends a first message to the first AMF entity. The first message includes first information, where the first information includes information requesting to establish a PDU session, and the information of the request to establish a PDU session includes a first parameter. The first message may be a NAS message, and the information requesting to establish a PDU session is used to request the SMF entity to establish a PDU session. 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 handover between access technologies according to at least one of a user equipment policy or a service.

For example, when the UE successfully registers in the 5G network, it receives a UE policy, for example, a UE routing selection policy (URSP). The UE determines that the data uploaded by the application according to the URSP should be transmitted on the PDU session that satisfies the condition. The PDU session is established if there is already a PDU session that satisfies the condition, and if not already, the UE initiates a PDU session establishment.

The UE may determine whether the PDU session supports handover between access technologies according to parameters corresponding to an access type (AT) in the URSP rule sent by the first AMF entity to the UE when the first AMF entity registers. As an example, the URSP rules can be seen in Table 1.

Table 1

Among them, the flow filter: information that can be compared with the data flow, and determines whether the rule is applicable to the data flow. It can include the application identifier and other information for its applicable data stream. The data stream that matches the flow filter of the URSP rule is called "matching traffic", which is the "matching stream" of the URSP rule.

Direct offload: Indicates that if the matching stream is disabled, the preferred or allowed (ie, allowed but not prioritized) non-3gpp access outside of the PDU session. It may also indicate a specific non-3GPP access type (eg WLAN, ssid-x), in which the matching stream is forbidden, preferred or allowed.

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

Continuity type: This includes the SSC mode required to match the stream. If the matching stream can be passed through a PDU session Support for any SSC mode, then it may also include multiple SSC modes in order of preference. It is used to associate matching traffic with one or more SSC modes.

DNNs: This includes the DNNs needed to match the stream. If a matching stream can be transferred to these DNNs through a PDU session, it may also contain multiple priority DNNs. It is used to associate a matching stream with one or more DNNs.

Access Type: If the UE needs to establish a PDU session for the matching stream, it indicates that the access type (3GPP or non-3GPP) of the PDU session should be established. It may also indicate the priority access list that should be attempted by the PDU session. The parameter corresponding to the access type directly indicates the 3GPP access and the N3GPP access, and the connection between the different access technologies is considered to be supported, or the URSP rule does not limit the access type. For example, the URSP rule has no access type. By default, it supports switching between different access technologies.

According to the information provided in Table 1, it can be determined that the PDU session corresponding to "DummyApp" is only allowed to be established through the 3GPP access technology, that is, the PDU session corresponding to "DummyApp" does not support the switching between access technologies, and "APP1" and " The PDU session corresponding to APP2" supports switching between access technologies.

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 the first AMF entity to indicate that the UE initiates the PDU session establishment and whether the PDU session supports the handover between the access technologies, where the first message carries the first parameter, and the PDU session is considered to be supported. When the first message does not carry the first parameter, the PDU session is considered to not support the switching between access technologies; or, when the first parameter value is 1, the PDU session is considered to be supported. When the first parameter value is 0, the PDU session is considered to not support switching between access technologies; vice versa.

For example, the first message may be a NAS message, where the NAS message includes a session ID, a DNN, and first information, where the first information may be “N1SM information”, and the N1SM information includes information of a PDU session establishment request. The information of the PDU session establishment request includes a first parameter, where the first parameter may be a handover indication (Handover Indication), where the handover indication is used to indicate that the PDU session supports handover between access technologies, for example, the handover indication is used for Indicates that the PDU session supports handover between 3GPP access technology and non-3GPP access technology.

S320. The first AMF entity determines a second parameter, where the second parameter is used to indicate that the UE is registered in the AMF by using an access technology.

If the UE is registered by only one access technology on the AMF entity (the first AMF entity), the UE may register on other AMF entities (the second AMF entity) through other access technologies. Therefore, after receiving the first message sent by the UE, the first AMF entity needs to determine whether the UE is registered by the access technology only in the first AMF. If the UE is registered by the first AMF only through one access technology, the first AMF determines the second parameter. If the UE is also registered by the other access technologies in the first AMF, it is not necessary to determine the second parameter. For example, the UE registers on the same AMF through the 3GPP access technology and the non-3GPP access technology.

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

S330. The first AMF entity sends a request to the SMF entity to invoke 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. The first service request is used to request to establish a PDU session.

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

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

For example, for the UE to register with the same AMF entity through the 3GPP access technology and the non-3GPP access technology, when the PDU session of the UE is switched from one access technology to another access technology, the DNN and the SMF used by the UE are unchanged. of. The AMF entity is changed for the UE to register with different AMF entities through the 3GPP access technology and the non-3GPP access technology.

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

The first AMF entity may determine the access technology registration status of the UE on the UE to notify the SMF entity. The first AMF entity may notify the SMF entity only when the UE registers on the UE through an access technology, that is, send the second parameter to the SMF entity,

For example, when the first AMF determines that the UE is registered thereon by only 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 to invoke the first service of the UDM entity.

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

After receiving the request of the first AMF entity to send the first service of the SMF entity, the SMF entity allocates an IP address for the PDU session corresponding to the request of the first service that invokes the SMF entity, and saves the session ID and the IP address. Corresponding relationship, so that the UE uses the IP address to communicate with a User Plane Function (UPF) entity and a data network.

The SMF entity also needs to register with the UDM entity, and register the information of the DNN and the SMF entity used by the PDU session of the UE, wherein the information of the SMF entity includes the identifier and/or address of the SMF entity, and the identifier of the SMF entity may be the SMF ID.

If the request for 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 with another AMF entity, and the SMF entity may not register with the UDM entity. Or, at the time of registration, the request to the UDM to call the service of the UDM entity may not include the DNN.

If the first information and the second parameter are included in the request to invoke the first service of the UDM entity, the SMF entity may consider that the UE may be registered with other AMF entities. The request sent by the SMF entity to the UDM to invoke the UDM entity may include a DNN. S350. The UDM entity determines, according to the access type, the second AMF entity that is registered by the UE by using the second access technology. If the second AMF entity exists, the UDM entity invokes the second service of the UDM entity, and notifies the second AMF entity to update the saved UE. Signing data, the subscription data of the UE includes information of the SMF entity and the SMF entity The DNN used by the managed PDU session.

If the request for invoking the first service of the UDM entity does not include information such as the DNN or the access type, the UDM entity updates the context of the corresponding UE saved by the UDM according to the request of the first service that invokes the UDM entity.

If the request to invoke the first service of the UDM entity includes information such as the DNN or the access type, the UDM entity updates the context of the corresponding UE saved by the UDM according to the request of the first service of the UDM entity. And determining, according to the access type, whether there is a second AMF entity that the UE registers with the second access technology, and if the second AMF entity exists, the UDM entity invokes the second service of the UDM entity, notifying the second AMF entity to update the second AMF entity. The subscription data of the saved UE, the subscription data of the UE includes information of the SMF entity and a DNN used by the PDU session managed by the SMF entity.

S360. The SMF entity sends a response to the first service of the SMF entity sent by the SMF entity, where the response of the first service that invokes the SMF entity includes the second information, where 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, where the second message includes 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.

With the embodiment of the present application, the UE may indicate to the AMF entity whether the PDU session that it is requesting to establish supports the handover between access technologies, so that the AMF entity determines, according to the registration status of the UE, when determining the handover between the PDU sessions and the access technologies. Whether you need to update to the UDM entity, or whether you need to update the DNN when updating. Thus, the SMF entity does not update the information to the UDM entity in all cases, or, in the update, not all cases update the DNN, saving signaling resources. 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 other AMF entities, so that the UDM entity combines the information sent by the SMF entity to determine that the UE is registered by other access technologies. When other AMF entities, the UE's subscription information is updated to other AMF entities, thereby saving signaling resources. The SMF does not update the UDM entity after receiving the corresponding indication, or sends the DNN to the UDM after the update, after receiving the corresponding indication, saving signaling resources. The UDM entity may determine, according to the access type, that when the UE registers with different AMF entities through different access technologies, the UDM entity may update the subscription data of the UE to the AMF entity other than the current AMF entity.

FIG. 4 is a schematic diagram of signaling interaction of another session establishment method according to an embodiment of the present disclosure. 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 includes first information, where the first information includes information requesting to establish a PDU session, and the information of the request to establish a PDU session includes a first parameter. The first message may be a NAS message, and the information requesting to establish a PDU session is used to request the SMF entity to establish a PDU session, where the first parameter is used to indicate that the session management function SMF entity registers the data used by the PDU session with the user data management UDM entity. The network name DNN and the identity and/or address of the SMF entity.

The UE may determine whether the PDU session supports handover between access technologies according to at least one of a user equipment policy or a service. For details, refer to the related description in the embodiment shown in FIG. 3, and details are not described herein again.

After determining that the PDU session supports handover between access technologies, the UE also needs to determine its registration with the first AMF entity.

When the UE determines that it is registered by the first AMF entity through an access technology, or the AMF entities registered and registered by the multiple access technologies are different, the first message carrying the first parameter is sent to the first AMF entity. The UE may determine the number of AMF entities it registers according to the number of Global User Temporary IDs (GUTIs) it holds. Generally, each UE registers an AMF entity, and the AMF entity can allocate a GUTI to the UE. When the UE holds one GUTI and registers with the first AMF entity through only one access technology, the UE determines that it is registered by the first AMF entity through one access technology, or when the UE holds multiple GUTIs, the UE It is determined that it is registered with the first AMF entity through an access technology. For example, the first message may be a NAS message, where the NAS message includes a session ID, a DNN, and first information, where the first information may be “N1SM information”, and the N1SM information includes information of a PDU session establishment request. The information of the PDU session establishment request includes a first parameter, where the first parameter may be a Handover Indication, where the handover indication is used to indicate that the SMF entity registers the data network name used by the PDU session with the user data management UDM entity. The DNN and the SMF entity, wherein the information of the SMF entity includes an identifier and/or an address of the SMF entity.

S420. The first AMF entity sends a request to the SMF entity to invoke the first service of the SMF entity, where the request for invoking the first service of the SMF entity includes the first information. The first service request is used to request to establish a PDU session.

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

When the UE initiates a PDU session establishment, the SMF entity corresponding to the PDU session needs to register with the UDM entity the data network name (DNN) used by the PDU session and the information of the SMF entity.

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

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

After receiving the request of the first AMF entity to send the first service of the SMF entity, the SMF entity allocates an IP address for the PDU session corresponding to the request of the first service that invokes the SMF entity, and saves the session ID and the IP address. Correspondence relationship 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, register the DNN used by the PDU session of the UE, and the information of the SMF entity.

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

If the first information is included in the request to invoke the first service of the SMF entity, the SMF entity may consider that the UE may have registered other AMF entities. The request sent by the SMF entity to the UDM to invoke the UDM entity may include a DNN. It may also include an access type corresponding to the PDU session. S440. The UDM entity determines, according to the access type, the second AMF entity that is registered by the UE by using the second access technology. If the second AMF entity exists, the UDM entity invokes the second service of the UDM entity, and notifies the second AMF entity to update the AMF entity to save. UE's subscription data, the UE The subscription data includes information of the SMF entity and the DNN used by the PDU session managed by the SMF entity.

For the step S440, reference may be made to the foregoing description of the step S350 in the embodiment shown in FIG. 3, and details are not described herein again.

S450. A response sent by the SMF entity to the AMF entity to invoke the first service of the SMF entity, where the response of the first service that invokes the SMF entity includes the second information, where the second information includes a PDU session establishment 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.

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.

With the embodiment of the present application, the UE may directly determine whether the PDU session supports handover between access technologies and the registration status of the UE. When both of the conditions are met, the SMF entity is instructed to register the information of the DNN and the SMF entity with the UDM entity. Therefore, the SMF entity does not update the information to the UDM entity in all cases, or not all cases, and carries the DNN when the SMF entity updates to the UDM entity, saving signaling resources. 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 other AMF entities, so that the UDM entity combines the information sent by the SMF entity to determine that the UE is registered by other access technologies. When other AMF entities, the UE's subscription information is updated to other AMF entities, thereby saving signaling resources. The SMF will not send information to the UDM entity after receiving the corresponding indication, or when the SMF entity updates to the UDM entity, the DNN is updated after receiving the corresponding indication, saving signaling resources. The UDM entity may determine, according to the access type, that when the UE registers with different AMF entities through different access technologies, the UDM entity may update the subscription data of the UE to the AMF entity other than the current AMF entity.

FIG. 5 is a schematic diagram of signaling interaction 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, a handover indication (Handover Indication). The UE may register whether the AMF entity is the same judgment according to the URSP rule and the access technology. If the parameters corresponding to the access type in the URSP rule indicate that both access technologies are available, the following two conditions are met: the UE is only registered by one access technology, or the UE is registered by two access technologies. And there are two different AMF entities (with two Global User Temporary IDs, GUTI). Then, when the UE determines that the SMF entity is registered in the UDM entity, the SMF entity needs to update the information of the SMF, and the DNN, the first parameter is determined.

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

S503. The AMF entity selects an SMF entity, and saves a correspondence between the session ID and the SMF ID and/or the address.

S504. The AMF entity sends a request to the SMF entity to invoke the first service of the SMF entity, where the request for the first service of the SMF entity includes the N1SM information received from the UE, where the request for the first service of the SMF entity is invoked. It can also include session ID, DNN, and access type.

S505. The SMF entity acquires UE subscription data from the UDM entity, where the UE subscription data includes the DNN, and Information about the SMF can be included.

S506. The SMF entity selects a UPF entity according to the DNN, allocates an IP address to the PUD session, and saves a correspondence between the session ID and the IP address, allocates a tunnel ID and an address to the UPF, and sends the same to the UPF to establish a PDU session with the UPF.

S507. The SMF entity sends a response to the AMF entity requesting the first service of the SMF entity, where the response of the request for the first service of the SMF entity may include an SM response, where the tunnel ID and address allocated by the SMF entity for the UPF entity are included. , and the PDU session establishes the accepted information (PDU session Est.Accept).

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

S509: The RAN entity sends the information about the PDU session establishment acceptance 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 RAN and the entity assigned tunnel ID and address are included.

S511, the AMF entity sends a request to the SMF entity to invoke the second service of the SMF entity, where the request for the second service of the SMF entity includes the N2 information, where the N2 information carries the SM request (SM Request with N2Info), where the SM request includes Receiving the tunnel ID and address assigned by the RAN sent by the RAN entity.

S512: The SMF entity performs PDU session modification on the UPF entity, and notifies the UPF entity of the tunnel ID and address allocated by the RAN entity, and the UPF entity sends the downlink data according to the tunnel ID and address allocated by the RAN entity.

S513. The SMF entity responds to the AMF entity with a response to the request of 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.

The information about the SMF entity corresponding to the DNN of the PDU session in the UDM may not be determined 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 to invoke the SMF first service.

If yes, the SMF entity may not register with the UDM entity, or call the first service of the UDM entity, and only update the information of the SMF entity corresponding to the DNN to the UDM entity, without updating the DNN, where the first service of the UDM entity is invoked. The request includes information about the SMF entity.

S515. If the information of the SMF entity corresponding to the DNN in the UE subscription information is not its own information, the SMF entity invokes the first service of the UDM entity to register the SMF (Register UE Serving SMF) of the UE service in the UDM entity. Among them, the content that needs to be registered includes DNN, SMF information, and access type.

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

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 respectively registered in different PLMNs, the SMF in the embodiment is the SMF of the HPLMN.

With the embodiment of the present application, the UE may indicate to the AMF entity whether the PDU session that it is requesting to establish supports the handover between access technologies, so that the AMF entity determines, according to the registration status of the UE, when determining the handover between the PDU sessions and the access technologies. Whether to update to the UDM entity, or when the SMF entity updates to the UDM entity, determine whether the DNN needs to be updated. Thus, the SMF entity does not update the information to the UDM entity in all cases, or the SMF entity does not update the DNN to the UDM entity in all cases, saving signaling resources. 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 other AMF entities, so that the UDM entity combines the information sent by the SMF entity to determine that the UE is registered by other access technologies. When other AMF entities, the UE's subscription information is updated to other AMF entities, thereby saving signaling resources. The SMF entity does not update the UDM entity after receiving the corresponding indication, or sends the DNN to the UDM when the SMF entity updates to the UDM entity after receiving the corresponding indication, saving signaling resources. The UDM entity may determine, according to the access type, that when the UE registers with different AMF entities through different access technologies, the UDM entity may update the subscription data of the UE to the AMF entity other than the current AMF entity.

FIG. 6 is a schematic diagram of signaling interaction of another session establishment method according to an 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, a handover indication (Handover Indication). 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 are available for the PDU session, 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, where the session ID, the DNN, and the N1SM information are included. The N1SM information includes a message requesting to establish a PDU session (PDU Session Establishment Request), where the information of the request to establish a PDU session includes a first parameter, where the first parameter is used for the UE to support handover between access technologies. The NAS message may be sent to the RAN entity in the RRC message, and sent by the RAN entity to the AMF entity. The RAN forwards the access type.

S603. The AMF entity selects an SMF entity, and saves a correspondence between the session ID and the SMF ID and/or the address.

If the AMF entity determines that the UE is registered by an access technology, the AMF entity determines that the second parameter needs to be sent to the SMF.

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

S605. The SMF entity acquires UE subscription data from the UDM entity, where the UE subscription data includes a DNN, and may further include an SMF ID and/or an address.

S606. The SMF entity selects the UPF entity according to the DNN, allocates an IP address to the PUD session, and saves the correspondence between the session ID and the IP address, assigns a tunnel ID and an address to the UPF, and sends the UPF to the UPF to establish a PDU session with the UPF.

S607. The SMF entity sends a response to the AMF entity requesting the first service of the SMF entity, and the response of the request for the first service of the SMF entity may include an SM response, where the tunnel ID and address allocated by the SMF entity for the UPF entity are included. , and the PDU session establishes the accepted information (PDU session Est.Accept).

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

S609. The RAN entity sends the information that the PDU session establishment accepts to the UE, and establishes a radio bearer of the PDU session.

S610. The RAN entity sends a PDU session request response to the AMF entity, where the RAN and the entity assigned tunnel ID and address are included.

S611, the AMF entity sends a request to the SMF entity to invoke the second service of the SMF entity, where the request for the second service of the SMF entity includes the N2 information, where the N2 information carries the SM request (SM Request with N2Info), where the SM request The tunnel ID and address of the RAN assignment sent by the RAN entity are received.

S612: The SMF entity performs PDU session modification on the UPF entity, and notifies 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.

S613. The SMF entity responds to the AMF entity with a response to the request of 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 itself. .

The information about the SMF entity corresponding to the DNN of the PDU session in the UDM may not be determined 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 is itself 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 to invoke 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 The first service of the UDM entity may be not registered, or the information of the SMF entity corresponding to the DNN may be updated only to the UDM entity without updating the DNN, wherein the request for calling the first service of the UDM entity includes the SMF entity. information.

S615. If the information of the SMF entity corresponding to the DNN in the UE subscription information is not its own information, the SMF entity invokes the second service of the UDM entity to register the SMF (Register UE Serving SMF) for the UE in the UDM entity. Among them, the content that needs to be registered includes DNN, SMF information, and access type.

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

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 respectively registered in different PLMNs, the SMF in the embodiment is the SMF of the HPLMN.

With the embodiment of the present application, the UE may directly determine whether the PDU session supports handover between access technologies and the registration status of the UE. When both of the conditions are met, the SMF entity is instructed to register the information of the DNN and the SMF entity with the UDM entity. Therefore, the SMF entity does not update the update to the UDM entity in all cases, or, after receiving the corresponding indication, when the SMF entity updates to the UDM entity, the SMF entity sends the DNN to the UDM, saving signaling. Resources. 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 other AMF entities, so that the UDM entity combines the information sent by the SMF entity to determine that the UE is registered by other access technologies. When other AMF entities update the UE to the other AMF entity Sign up information to save signaling resources. The SMF does not update the UDM entity after receiving the corresponding indication, or, after receiving the corresponding indication, when the SMF entity updates to the UDM entity, the SMF entity sends the DNN to the UDM, saving signaling resources. The UDM entity may determine, according to the access type, that when the UE registers with different AMF entities through different access technologies, the UDM entity may update the subscription data of the UE to the AMF entity other than the current AMF entity.

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

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

The receiving unit 702 is configured to receive a second message sent by the AMF entity, where the second message includes the second information, where the second information includes information that the PDU session establishment accepts.

Optionally, the UE further includes:

The 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: when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not include the access type, determine the first parameter .

Optionally, the sending unit 701 is further configured to: when the UE is registered by using an access technology, or the UE is registered by multiple access technologies and the registered AMF entities are different, sending the first message to the AMF entity, the first message. The first information is included, the first information includes information for requesting to establish a PDU session, and the information for requesting to establish a PDU session includes a first parameter, where the first parameter is used to instruct the SMF entity to register the DNN used by the PDU session with the information of the SMF entity and the SMF entity.

The UE may function as a UE of the session establishment method as described in FIGS. 3 to 6, and perform the steps performed by the UE in FIGS. 3 to 6. Therefore, the network device can determine, according to the information provided by the UE, the support of the handover between different access technologies of the PDU session, and even if the UE registers with the network side, determine whether it needs to be updated to the UDM entity, or when the SMF entity goes to the UDM entity. Upon update, the SMF entity determines if the DNN needs to be updated to the UDM entity. Therefore, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM entity, the SMF entity does not update the DNN to the UDM entity in all cases, saving signaling resources. .

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:

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

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

The receiving unit 801 is further configured to receive, by the SMF entity, a response of the first service that invokes the SMF entity, and the response of the first service that invokes the SMF entity includes the second information, where the second information includes information that the PDU session establishes acceptance;

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 indicate that the UE is registered in the AMF by using an access technology;

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

The AMF entity may serve as an AMF entity of the session establishment method as described in FIGS. 3 through 6, and perform the steps performed by the UE in FIGS. 3 through 6. Therefore, the SMF entity can determine the support of the handover between different access technologies of the PDU session according to the information provided by the UE and the AMF entity, and even determine whether the UE needs to be updated to the UDM entity when the UE is registered on the network side, or when the SMF entity When updating to a UDM entity, the SMF entity determines if the DNN needs to be updated to the UDM entity. Thus, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM entity, the SMF entity does not update the DNN to the UDM entity in all cases, saving signaling resources. .

FIG. 9 is a schematic structural diagram of an SMF entity according to an embodiment of the present application. As shown in FIG. 9, the SMF entity may include:

The receiving unit 901 is configured to receive, by the first access and the mobile management function, the AMF entity, the request for calling the first service of the SMF entity, where the request for calling the first service of the SMF entity includes the first information, where the first information includes a request to establish a protocol. The information of the data unit PDU session, the information requesting to establish the PDU session includes a first parameter, the first parameter indicates that the PDU session supports handover between different access technologies, or indicates that the SMF entity registers the data network used by the PDU session with the user data management UDM entity. Name DNN and SMF information;

The sending unit 902 is configured to send, to the first AMF entity, a response that invokes the first service of the SMF entity, and the response of the first service that invokes the SMF entity includes the second information, where the second information includes information that the PDU session establishes acceptance.

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 that establishes the PDU session passes the The access technology is registered in the first AMF.

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

The SMF entity may serve as an SMF entity of the session establishment method as described in FIGS. 3 through 6, and perform the steps performed by the UE in FIGS. 3 through 6. Therefore, the SMF entity can determine the support of the handover between different access technologies of the PDU session according to the information provided by the UE and the AMF entity, and even determine whether the UE needs to be updated to the UDM entity when the UE is registered on the network side, or when the SMF entity When updating to a UDM entity, the SMF entity determines if the DNN needs to be updated to the UDM entity. Thus, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM entity, the SMF entity does not update the DNN to the UDM entity in all cases, saving signaling resources. .

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:

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

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

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

The UDM entity may function as a UDM entity of the session establishment method as described in FIGS. 3 to 6, and perform the steps performed by the UE in FIGS. 3 to 6. The UDM entity can determine whether the PDU session supports the handover between different access technologies according to the information provided by the UE and the AMF entity, and even if the UE registers with the network side, determine whether the UE subscription information needs to be updated to other AMF entities. Thus, the UDM does not update the subscription information of the UE to all AMF entities registered with the UE, thereby saving signaling resources.

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

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

The receiver 1102 is configured to receive a second message sent by the AMF entity, where the second message includes the second information, where the second information includes information that the PDU session establishment accepts.

Optionally, the UE further includes:

The processor 1103 is 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: when the access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not include the access type, determine the first parameter. .

Optionally, the transmitter 1101 is further configured to: when the UE is registered by using an access technology, or the UE is registered by multiple access technologies and the registered AMF entities are different, sending the first message to the AMF entity, the first message. The first information is included, the first information includes information for requesting to establish a PDU session, and the information for requesting to establish a PDU session includes a first parameter, where the first parameter is used to instruct the SMF entity to register the DNN used by the PDU session with the information of the SMF entity and the SMF entity.

In addition, the UE provided by the embodiment of the present application may further include a memory and a processor 1103. The memory is used to store corresponding instructions and data, so that the processor can retrieve the instructions of the memory and process the data accordingly.

The UE may function as a UE of the session establishment method as described in FIGS. 3 to 6, and perform the steps performed by the UE in FIGS. 3 to 6. Therefore, the network device can determine, according to the information provided by the UE, the support of the handover between different access technologies of the PDU session, and even if the UE registers with the network side, determine whether it needs to be updated to the UDM entity, or when the SMF entity goes to the UDM entity. Upon update, the SMF entity determines if the DNN needs to be updated to the UDM entity. Therefore, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM entity, the SMF entity does not update the DNN to the UDM entity in all cases, saving signaling resources. .

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:

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

The sender 1202 is configured to send, to the SMF entity, a request for invoking a first service of the SMF entity, where the request for calling the first service of the SMF entity includes the first information;

The receiver 1201 is further configured to receive, by the SMF entity, a response of the first service that invokes the SMF entity, and the response of the first service that invokes the SMF entity includes the second information, where the second information includes information that the PDU session establishes acceptance;

The transmitter 1202 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:

The processor 1203 is configured to determine a second parameter, where the second parameter is used to indicate that the UE is registered in the AMF by using an access technology;

The sender 1202 is further configured to send a request to the SMF entity 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.

In addition, optionally, the AMF entity provided by the embodiment of the present application may further include a memory and a processor 1203. The memory is used to store corresponding instructions and data, so that the processor can retrieve the instructions of the memory and process the data accordingly.

The AMF entity may serve as an AMF entity of the session establishment method as described in FIGS. 3 through 6, and perform the steps performed by the UE in FIGS. 3 through 6. Therefore, the SMF entity can determine the support of the handover between different access technologies of the PDU session according to the information provided by the UE and the AMF entity, and even determine whether the UE needs to be updated to the UDM entity when the UE is registered on the network side, or when the SMF entity When updating to a UDM entity, the SMF entity determines if the DNN needs to be updated to the UDM entity. Thus, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM entity, the SMF entity does not update the DNN to the UDM entity in all cases, saving signaling resources. .

FIG. 13 is a schematic structural diagram of an SMF entity according to an embodiment of the present application. As shown in FIG. 13, the SMF entity may include:

The receiver 1301 is configured to receive, by the first access and the mobile management function, the AMF entity, a request for calling the first service of the SMF entity, where the request for calling the first service of the SMF entity includes the first information, where the first information includes a request to establish a protocol. The information of the data unit PDU session, the information requesting to establish the PDU session includes a first parameter, the first parameter indicates that the PDU session supports handover between different access technologies, or indicates that the SMF entity registers the data network used by the PDU session with the user data management UDM entity. Name DNN and SMF information;

The sender 1302 is configured to send a response to the first AMF entity that invokes the first service of the SMF entity, and the response of the first service that invokes the SMF entity includes the second information, where the second information includes information that the PDU session establishment accepts.

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 that establishes the PDU session passes the The access technology is registered in the first AMF.

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

In addition, the SMF entity provided by the embodiment of the present application may further include a memory and a processor 1303. The memory is used to store corresponding instructions and data, so that the processor can retrieve the instructions of the memory and process the data accordingly.

The SMF entity may serve as an SMF entity of the session establishment method as described in FIGS. 3 through 6, and perform the steps performed by the UE in FIGS. 3 through 6. Thereby the SMF entity can determine the PDU according to the information provided by the UE and the AMF entity. The support of the session for the handover between different access technologies, even if the UE is registered on the network side, determines whether it needs to be updated to the UDM entity, or when the SMF entity updates to the UDM entity, the SMF entity determines whether it needs to update to the UDM entity. DNN. Thus, the SMF entity does not update the information to the UDM entity in all cases, or when the SMF entity updates to the UDM entity, the SMF entity does not update the DNN to the UDM entity in all cases, saving signaling resources. .

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:

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

The processor 1402 is configured to determine, according to the access type, a second AMF entity that is registered by the UE by using the second access technology;

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

The UDM entity may function as a UDM entity of the session establishment method as described in FIGS. 3 to 6, and perform the steps performed by the UE in FIGS. 3 to 6. The UDM entity can determine whether the PDU session supports the handover between different access technologies according to the information provided by the UE and the AMF entity, and even if the UE registers with the network side, determine whether the UE subscription information needs to be updated to other AMF entities. Thus, the UDM does not update the subscription information of the UE to all AMF entities registered with the UE, thereby saving signaling resources.

Embodiments of the present application provide a computer program product comprising instructions that, when executed on a computer, perform the methods/steps of Figures 3 through 6 above.

The embodiment of the present application provides a computer readable storage medium for storing instructions, when the instructions are executed on a computer, performing the methods/steps in FIG. 3 to FIG. 6 above.

In each of the above embodiments of the present invention, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it 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 the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable medium to another computer readable medium, for example, the computer instructions can be wired from a website site, computer, server or data center (for example, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) to another website site, computer, server or data center. The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state hard disk) or the like.

The above description is only a preferred embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed in the present application. Replacement should be covered by the scope of this application. Therefore, the scope of protection of the present application should be determined by the scope of protection of the claims.

Claims (32)

A session establishing method, comprising: The user equipment UE sends a first message to the access and mobility management function AMF entity, the first message comprising first information, the first information comprising information requesting to establish a protocol data unit PDU session, the request establishing a PDU session The information includes a first parameter, the first parameter is used to indicate that the PDU session supports handover between different access technologies, or the session management function SMF entity is configured to register the data network name used by the PDU session with the unified data management UDM entity. DNN and information of the SMF entity; The UE receives a second message sent by the AMF entity, the second message includes second information, and the second information includes information that the PDU session establishment accepts. The method according to claim 1, wherein 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. The method according to claim 2, wherein the determining, by the UE, the first parameter according to a user equipment policy comprises: The UE determines the first parameter when an access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not limit an access type. The method according to any one of claims 1-3, wherein the UE sends a first message to an AMF entity, the first message includes first information, and the first information includes requesting to establish a PDU session. The information of the request to establish a PDU session includes a first parameter, where the first parameter is used to indicate that the SMF entity registers the DNN used by the PDU session with the information of the SMF entity, and the information includes: When the UE is registered by an 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, where the first message includes For information, the first information includes information requesting to establish a PDU session, and the information for requesting to establish a PDU session includes a first parameter, where the first parameter is used to instruct the SMF entity to register the DNN used by the PDU session with the UDM entity. And information about the SMF entity. A session establishing method, comprising: The access and mobility management function AMF entity receives the first message sent by the user equipment UE, the first message includes first information, the first information includes information requesting to establish a protocol data unit PDU session, and the request establishes a PDU session The information includes a first parameter, the first parameter is used to indicate that the PDU session supports handover between different access technologies, or the session management function SMF entity is configured to register a data network used by the PDU session with the unified data management UDM entity. Name DNN and information of the SMF; Sending, by the AMF entity, a request for invoking a 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; The AMF entity receives a response sent by the SMF entity to invoke a first service of the SMF entity, the response of the first service that invokes the SMF entity includes second information, and the second information includes a PDU session establishment. Information received; The AMF entity sends a fourth message to the UE, where the fourth message includes the second information. The method according to claim 5, wherein the AMF entity receives a first message sent by the UE, the first message includes first information, and the first information includes information requesting to establish a PDU session, where Description The information for requesting to establish a PDU session includes a first parameter, where the first parameter is used to indicate that the PDU session supports switching between different access technologies, and further includes: Determining, by the AMF entity, a second parameter, where the second parameter is used to indicate that the UE is registered in the AMF by using an access technology; The AMF entity sends a request to the session management function SMF entity 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, specifically: the AMF entity Sending, to the SMF entity, the 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. A session establishing method, comprising: The session management function SMF entity receives a request sent by the first access and mobility management function AMF entity to invoke the first service of the SMF entity, where the request for invoking the first service of the SMF entity includes first information, The first information includes information for requesting establishment of a protocol data unit PDU session, the information of the request to establish a PDU session includes a first parameter, the first parameter indicating that the PDU session supports handover between different access technologies, or indicating the The SMF entity registers the data network name DNN used by the PDU session with the user data management UDM entity and the information of the SMF; Sending, by the SMF entity, a response to the first AMF entity that invokes the first service of the SMF entity, the response of the first service that invokes the SMF entity includes second information, and the second information includes a PDU session Establish accepted information. The method according to claim 7, wherein when the first parameter indicates that the PDU session supports handover between different access technologies, the request to invoke the first service of the SMF entity further includes a second parameter The second parameter is used to indicate that the UE that establishes the PDU session is registered in the first AMF by using an access technology. The method according to claim 7 or 8, further comprising: The SMF entity sends a request to the UDM entity to invoke a first service of the UDM entity, the request to invoke the first service of the UDM entity includes information of a DNN used by the PDU session and the SMF entity. A session establishing method, comprising: The user data management UDM entity receives a request sent by the session management function SMF entity to invoke the first service of the UDM entity, and the request to invoke the first service of the UDM entity includes an access type, and the access type is used for And the UE corresponding to the PDU session managed by the SMF entity is registered by the first AMF entity by using the first access technology; Determining, by the UDM entity, the second AMF entity that is registered by the UE by using the second access technology, according to the access type, if the second AMF entity exists, the UDM entity invokes the second service of the UDM entity And notifying the second AMF entity to update the saved subscription data of the UE, where the subscription data of the UE includes information of the SMF entity and a DNN used by the MF session managed by the SMF entity. A user equipment (UE), comprising: And a transmitter, configured to send a first message to the access and mobility management function AMF entity, where the first message includes first information, where the first information includes information requesting to establish a protocol data unit PDU session, where the request establishes a PDU The information of the session includes a first parameter, the first parameter is used to indicate that the PDU session supports handover between different access technologies, or the session management function SMF entity is configured to register the PDU session with the unified data management UDM entity. Data network name DNN and information of the SMF entity; And a receiver, configured to receive a second message sent by the AMF entity, where the second message includes second information, where the second information includes information that the PDU session establishment accepts. The UE according to claim 11, further comprising: And a processor, configured to determine the first parameter according to at least one of a user equipment policy or a service. The UE according to claim 12, wherein the processor is further configured to: when an access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not limit an access type The first parameter is determined. The UE according to any one of claims 11 to 13, wherein the transmitter is further configured to: when the UE is registered by using an access technology, or the UE is registered by using multiple access technologies. When the registered AMF entity is different, the first message is sent to the AMF entity, where the first message includes first information, the first information includes information for requesting to establish a PDU session, and the information for requesting to establish a PDU session includes the first a parameter, the first parameter is used to instruct the SMF entity to register the DNN used by the PDU session with the UDM entity and the information of the SMF entity. An access and mobility management function AMF entity, comprising: a receiver, configured to receive a first message sent by the 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, where the information of the request to establish a PDU session includes a first parameter, the first parameter is used to indicate that the PDU session supports handover between different access technologies, or that the session management function SMF entity registers the data network name DNN used by the PDU session with the unified data management UDM entity and Information of the SMF; a sender, configured to send, to the 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 the first information; The receiver is further configured to receive a response sent by the SMF entity to invoke a first service of the SMF entity, where the response of the first service that invokes the SMF entity includes second information, the second information Including PDU session establishment acceptance information; The transmitter is further configured to send a fourth message to the UE, where the fourth message includes the second information. The AMF entity according to claim 15, further comprising: a processor, configured to determine a second parameter, where the second parameter is used to indicate that the UE is registered in the AMF by using an access technology; The sender 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 The second parameter. A session management function SMF entity, comprising: a receiver, configured to receive, by the first access and mobility management function, an AMF 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, where The first information includes information for requesting establishment of a protocol data unit PDU session, the information of the request to establish a PDU session includes a first parameter, the first parameter indicating that the PDU session supports handover between different access technologies, or indicating the The SMF entity registers the data network name DNN used by the PDU session with the user data management UDM entity and the information of the SMF; a transmitter, configured to send, to the first AMF entity, a response to invoke a first service of the SMF entity, where the response of the first service that invokes the SMF entity includes second information, where the second information includes a PDU Session establishment Information received. The SMF entity according to claim 17, wherein when the first parameter indicates that the PDU session supports handover between different access technologies, the request to invoke the first service of the SMF entity further includes a second a parameter, the second parameter is used to indicate that the UE that establishes the PDU session is registered in the first AMF by using an access technology. The SMF entity according to claim 17 or 18, wherein the sender is further configured to send a request to the UDM entity to invoke a first service of the UDM entity, the first call of the UDM entity The request for the service includes the DNN used by the PDU session and the address and/or identity of the SMF entity. A user data management UDM entity, comprising: a receiver, configured to receive a request sent by a session management function SMF entity to invoke a first service of the UDM entity, where the request for invoking the first service of the UDM entity includes an access type, where the access type is used And the UE corresponding to the PDU session managed by the SMF entity is registered by the first AMF entity by using the first access technology; a processor, configured to determine, according to the access type, a second AMF entity that is registered by the UE by using a second access technology; a transmitter, configured to: if the second AMF entity exists, invoke a second service of the UDM entity, to notify the second AMF entity to update the saved subscription data of the UE, where the subscription data of the UE includes The information of the SMF entity and the DNN used by the PDU session managed by the SMF entity. A user equipment (UE), comprising: And a sending unit, configured to send a first message to the access and mobility management function AMF entity, where the first message includes first information, where the first information includes information requesting to establish a protocol data unit PDU session, where the request establishes a PDU The information of the session includes a first parameter, the first parameter is used to indicate that the PDU session supports handover between different access technologies, or the session management function SMF entity is configured to register data used by the PDU session with the unified data management UDM entity. Network name DNN and information of the SMF entity; And a receiving unit, configured to receive a second message sent by the AMF entity, where the second message includes second information, where the second information includes information that the PDU session establishment accepts. The UE according to claim 21, further comprising: And a determining unit, configured to determine the first parameter according to at least one of a user equipment policy or a service. The UE according to claim 22, wherein the determining unit is further configured to: when an access type in the user equipment policy indicates multiple access technologies, or the user equipment policy does not limit an access type The first parameter is determined. The UE according to any one of claims 21 to 23, wherein the sending unit is further configured to: when the UE is registered by using an access technology, or the UE is registered by using multiple access technologies. When the registered AMF entity is different, the first message is sent to the AMF entity, where the first message includes first information, the first information includes information for requesting to establish a PDU session, and the information for requesting to establish a PDU session includes the first a parameter, the first parameter is used to instruct the SMF entity to register the DNN used by the PDU session with the UDM entity and the information of the SMF entity. An access and mobility management function AMF entity, comprising: a receiving unit, configured to receive a first message sent by the 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, where the request establishes information of a PDU session And including a first parameter, where the first parameter is used to indicate that the PDU session supports handover between different access technologies, or that the session management function SMF entity registers the data network name DNN used by the PDU session with the unified data management UDM entity. And the information of the SMF; a sending unit, configured to send, to the 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 the first information; The receiving unit is further configured to receive a response sent by the SMF entity to invoke a first service of the SMF entity, where the response of the first service that invokes the SMF entity includes second information, where the second information is Including PDU session establishment acceptance information; The sending unit is further configured to send a fourth message to the UE, where the fourth message includes the second information. The AMF entity of claim 25, further comprising: a determining unit, configured to determine a second parameter, where the second parameter is used to indicate that the UE is registered in the AMF by using an access technology; The sending unit is further configured to send the request for calling 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 The second parameter. A session management function SMF entity, comprising: a receiving unit, configured to receive a request that is sent by the first access and mobility management function AMF entity to invoke the first service of the SMF entity, where the request for invoking the first service of the SMF entity includes first information, where The first information includes information for requesting establishment of a protocol data unit PDU session, the information of the request to establish a PDU session includes a first parameter, the first parameter indicating that the PDU session supports handover between different access technologies, or indicating the The SMF entity registers the data network name DNN used by the PDU session with the user data management UDM entity and the information of the SMF; a sending unit, configured to send, to the first AMF entity, a response to invoke a first service of the SMF entity, where the response of the first service that invokes the SMF entity includes second information, where the second information includes a PDU The session establishes the accepted information. The SMF entity according to claim 27, wherein when the first parameter indicates that the PDU session supports handover between different access technologies, the request to invoke the first service of the SMF entity further includes a second a parameter, the second parameter is used to indicate that the UE that establishes the PDU session is registered in the first AMF by using an access technology. The SMF entity according to claim 27 or 28, wherein the sending unit is further configured to send, to the UDM entity, a request to invoke a first service of the UDM entity, the first call of the UDM entity The request for the service includes the DNN used by the PDU session and the address and/or identity of the SMF entity. A user data management UDM entity, comprising: a receiving unit, configured to receive a request sent by a session management function SMF entity to invoke a first service of the UDM entity, where the request for invoking the first service of the UDM entity includes an access type, where the access type is used And the UE corresponding to the PDU session managed by the SMF entity is registered by the first AMF entity by using the first access technology; a determining unit, configured to determine, according to the access type, a second AMF entity that is registered by the UE by using a second access technology; a sending unit, configured to: if the second AMF entity exists, invoke a second service of the UDM entity, to notify the second AMF entity to update the saved subscription data of the UE, where the subscription data of the UE includes Description Information of the SMF entity and the DNN used by the PDU session managed by the SMF entity. 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 of claims 1-10. A computer program product comprising computer readable instructions which, when read and executed by a computer, cause a computer to perform the method of any of claims 1-10.

Images