CN109246769B

CN109246769B - PDU session establishment method and device

Info

Publication number: CN109246769B
Application number: CN201710313933.XA
Authority: CN
Inventors: 熊春山; 孙海洋; 吴义壮
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-05-05
Filing date: 2017-05-05
Publication date: 2020-10-09
Anticipated expiration: 2037-05-05
Also published as: CN109246769A; WO2018201989A1

Abstract

The application discloses a PDU session establishment method and device. The method comprises the following steps: the terminal determines whether the PDU session to be established is allowed to be locally dredged or not according to the roaming strategy included in the first message, and generates a PDU session establishment request; because the PDU session establishment request comprises the first indication information used for indicating whether the PDU session to be established is allowed to be locally dredged or not, the AMF network element receiving the PDU session establishment request can generate the session management request according to the first indication information, and then the PDU session of the HPLMN or the PDU session of the VPLMN is established. Compared with the prior art that the PDU conversation to be established is identified according to the SM container and the home routing is required to be carried out, the scheme in the application only uses one SM container without increasing the number of the SM containers, and further effectively avoids the problem that NAS information is complex.

Description

PDU session establishment method and device

Technical Field

The present application relates to the field of wireless communications technologies, and in particular, to a PDU session establishment method and apparatus.

Background

In the next generation wireless communication system, for example: in a New Radio (NR) system, a terminal establishes a Protocol Data Unit (PDU) session with a Data Network (DN) Network element through a User Plane Function (UPF) Network element, and the PDU session provides a PDU connection service between the terminal and the DN Network element.

When the terminal is located at the Home, the PDU session for providing the PDU connection service is a PDU session of a Home Public Land Mobile Network (HPLMN); when the terminal is located in a Visited place (i.e., a roaming scenario), one possible scenario is to perform home-routed (home-routed), at which time the PDU session for providing the PDU connection service is a PDU session of the HPLMN, and another possible scenario is to perform local breakout (local breakout), at which time the PDU session for providing the PDU connection service is a PDU session of a Visited Public Land Mobile Network (VPLMN). In roaming scenarios, some specific services have specific requirements for the PDU session, for example, the PDU session of the HPLMN must be used to provide the PDU connection service. Therefore, when a PDU session is established, it needs to be identified whether the PDU session to be established must be subjected to home routing, so as to ensure normal transmission of data traffic.

Disclosure of Invention

The application provides a PDU session establishment method and device, which are used for effectively identifying whether the PDU session to be established needs to be subjected to home routing or not and ensuring normal transmission of data services.

In a first aspect, the present application provides a PDU session establishment method, including:

a terminal receives a first message, wherein the first message comprises a roaming policy of the terminal;

the terminal determines whether the PDU session to be established is allowed to be locally dredged or not according to the roaming strategy, and generates a PDU session establishment request; the PDU conversation establishing request comprises first indication information used for indicating whether the PDU conversation to be established allows local breakout or not;

and the terminal sends the PDU session establishment request to an access and mobility management function (AMF) network element.

Thus, the terminal determines whether the PDU session to be established is allowed to carry out local breakout or not according to the roaming strategy included in the first message, and generates a PDU session establishment request; because the PDU session establishment request comprises the first indication information used for indicating whether the PDU session to be established is allowed to be locally dredged or not, the AMF network element receiving the PDU session establishment request can generate the session management request according to the first indication information, and then the PDU session of the HPLMN or the PDU session of the VPLMN is established. Compared with the prior art that the PDU conversation to be established must be subjected to home routing according to SM container identification, the scheme in the application only uses one SM container, the number of the SM containers is not required to be increased, and the problem that NAS information is complex is effectively avoided.

With reference to the first aspect, in a first possible implementation manner of the first aspect, the roaming policy includes a type of a PDU session that is not allowed to be locally groomed;

the terminal determines whether the PDU session to be established is allowed to carry out local breakout according to the roaming strategy, and the method comprises the following steps:

and the terminal determines that the type of the PDU session to be established belongs to the type of the PDU session which is not allowed to carry out local breakout and is included in the roaming strategy, and determines that the PDU session to be established is not allowed to carry out local breakout.

Therefore, the terminal can determine whether the PDU session to be established is allowed to be subjected to local breakout by judging whether the type of the PDU session to be established belongs to the type of the PDU session which is not allowed to be subjected to local breakout, and the implementation process is simple and quick.

With reference to the first aspect, in a second possible implementation manner of the first aspect, the roaming policy includes a correspondence between a type of the PDU session and a roaming identifier; the roaming identifier is used for indicating whether the PDU session belonging to the type corresponding to the roaming identifier allows local breakout;

and the terminal determines a roaming identifier corresponding to the type of the PDU session to be established according to the type of the PDU session to be established and the roaming strategy.

With reference to the first aspect and the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the allowing for local breakout for the PDU session to be established includes:

the PDU session to be established allows local breakout and requires home public land mobile network HPLMN authorization; alternatively, the first and second electrodes may be,

the PDU session to be established allows local breakout without requiring HPLMN authorization.

In a second aspect, the present application provides a PDU session establishment method, including:

the method comprises the steps that an AMF network element receives a PDU session establishment request from a terminal, wherein the PDU session establishment request comprises first indication information used for indicating whether a PDU session to be established is allowed to be locally dredged or not;

and the AMF network element generates a session management request according to the first indication information and sends the session management request, wherein the session management request is used for requesting to establish the PDU session.

With reference to the second aspect, in a first possible implementation manner of the second aspect, when the first indication information indicates that the PDU session to be established is not allowed to be locally groomed, the session management request includes identification information of an SMF network element of a home location selected by the AMF network element, and the session management request is used to request establishment of a PDU session of an HPLMN.

With reference to the second aspect, in a second possible implementation manner of the second aspect, when the first indication information indicates that the to-be-established PDU session is allowed to be locally breakout, the session management request is used to request establishment of a PDU session of a VPLMN.

With reference to the second aspect and the second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, when the first indication information indicates that the PDU session to be established is allowed to be locally groomed and needs to be authorized by the HPLMN, the session management request includes second indication information for indicating that the PDU session to be established needs to be authorized by the HPLMN, and the session management request is used for requesting that authorization by the HPLMN is performed and establishing a PDU session of the VPLMN.

In a third aspect, the present application provides a terminal, including: a receiver, a transmitter and a processor;

the receiver is configured to receive a first message, where the first message includes a roaming policy of the terminal;

the processor is used for determining whether the PDU session to be established is allowed to be locally dredged or not according to the roaming strategy and generating a PDU session establishment request; the PDU conversation establishing request comprises first indication information used for indicating whether the PDU conversation to be established allows local breakout or not;

and the sender is used for sending the PDU session establishment request to an access and mobility management function (AMF) network element.

With reference to the third aspect, in a first possible implementation manner of the third aspect, the roaming policy includes a type of a PDU session that is not allowed to perform local breakout;

the processor is specifically configured to:

and if the type of the PDU session to be established belongs to the type of the PDU session which is not allowed to carry out local breakout and is included in the roaming strategy, determining that the PDU session to be established is not allowed to carry out local breakout.

With reference to the third aspect, in a second possible implementation manner of the third aspect, the roaming policy includes a correspondence between a type of the PDU session and a roaming identifier; the roaming identifier is used for indicating whether the PDU session belonging to the type corresponding to the roaming identifier allows local breakout;

the processor is specifically configured to:

and determining a roaming identifier corresponding to the type of the PDU session to be established according to the type of the PDU session to be established and the roaming strategy.

With reference to the third aspect and the second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the allowing local breakout for the PDU session to be established includes:

In a fourth aspect, the present application provides an AMF network element, where the AMF network element includes: a receiver, a transmitter and a processor;

the receiver is configured to receive a PDU session establishment request from a terminal, where the PDU session establishment request includes first indication information used to indicate whether a PDU session to be established allows local breakout;

the processor is used for generating a session management request according to the first indication information;

the sender is configured to send the session management request, where the session management request is used to request establishment of the PDU session.

With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, when the first indication information indicates that the PDU session to be established is not allowed to be locally groomed, the session management request includes identification information of an SMF network element of a home location selected by the AMF network element, and the session management request is used to request establishment of a PDU session of an HPLMN.

With reference to the fourth aspect, in a second possible implementation manner of the fourth aspect, when the first indication information indicates that the to-be-established PDU session is allowed to be locally groomed, the session management request is used to request establishment of a PDU session of a VPLMN.

With reference to the fourth aspect and the second possible implementation manner of the fourth aspect, in a third possible implementation manner of the fourth aspect, when the first indication information indicates that the PDU session to be established is allowed to be locally groomed and needs to be authorized by the HPLMN, the session management request includes second indication information used for indicating that the PDU session to be established needs to be authorized by the HPLMN, and the session management request is used for requesting that authorization by the HPLMN is performed and establishing a PDU session of the VPLMN.

In a fifth aspect, the present application provides a communication entity, where the communication entity is configured to execute a method procedure executed by a terminal in the PDU session establishment method. The communication entity may be a terminal.

In a sixth aspect, the present application provides a communication entity, where the communication entity is configured to execute a method procedure executed by an AMF network element in the PDU session establishment method. The communication entity may be an AMF network element.

In the application, the terminal determines whether the PDU session to be established is allowed to be locally dredged or not according to the roaming strategy included in the first message, and generates a PDU session establishment request; because the PDU session establishment request comprises the first indication information used for indicating whether the PDU session to be established is allowed to be locally dredged or not, the AMF network element receiving the PDU session establishment request can generate the session management request according to the first indication information, and then the PDU session of the HPLMN or the PDU session of the VPLMN is established. Compared with the prior art that the PDU conversation to be established must be subjected to home routing according to SM container identification, the scheme in the application only uses one SM container, the number of the SM containers is not required to be increased, and the problem that NAS information is complex is effectively avoided.

Drawings

FIG. 1 is a schematic diagram of a possible 5G network architecture;

FIG. 2A is a network architecture diagram of a home routing scenario;

fig. 2B is a network architecture diagram of a first local breakout scenario;

fig. 2C is a network architecture diagram of a second local breakout scenario;

fig. 3 is a schematic flowchart illustrating a PDU session establishment method according to an embodiment of the present application;

fig. 4 is a schematic diagram of a PDU session establishment process in the second embodiment of the present application;

fig. 5 is a schematic diagram of a PDU session establishment process in the third embodiment of the present application;

fig. 6 is a schematic diagram of a PDU session establishment process in the fourth embodiment of the present application;

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

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

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

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

Detailed Description

The embodiments of the present application will be described in detail below with reference to the drawings attached to the specification.

The embodiment of the application can be applied to various mobile communication systems, such as: global System for Mobile communications (GSM) System, Code Division Multiple Access (CDMA) System, Wideband Code Division Multiple Access (WCDMA) System, General Packet Radio Service (GPRS), Long Term Evolution (Long Term Evolution, LTE) System, LTE-a System, UMTS (Universal Mobile telecommunications System, UMTS), LTE (evolved Long Term Evolution), and 5G (e.g., NR System).

In the 5G network architecture in question, there are a number of possible architectures. Fig. 1 is a schematic diagram of a possible 5G Network architecture, as shown in fig. 1, the Network architecture includes an Authentication Server Function (AUSF) Network element, a Unified Data Management Function (UDM) Network element, an Access and Mobility Management Function (AMF) Network element, a Session Management Function (SMF) Network element, a Policy Control Function (PCF) Network element, an Application Function (AF) Network element, a Radio Access Network (RAN) Network element (also referred to as an Access Network element), a User Plane Function (User Plane Function, UPF) Network element, a Data Network (DataNetwork, DN) Network element, a terminal, and the like.

The SMF network element is responsible for session management, terminal Internet Protocol (IP) address allocation and management, and the like. The AMF network element is responsible for access and mobility Management, is a termination point of an NG2 (interface between the AMF and the RAN device) interface, terminates a Non-access stratum (NAS) message, completes registration Management, connection Management, reachability Management, mobility Management, and the like, and transparently routes a Session Management (SM) message to the SMF network element. The UPF network element is a user plane function device and is responsible for routing and forwarding of data packets, legal monitoring, downlink data packet caching, triggering downlink data packet notification messages and other functions.

In the present application, the terminal may be a wireless terminal for providing voice and/or data connectivity to a user. The wireless terminal may be a handheld device having wireless connection capabilities, or other processing device connected to a wireless modem, a mobile terminal communicating with one or more core networks via a radio access network. For example, the wireless terminal may be a mobile phone, a computer, a tablet computer, a Personal Digital Assistant (PDA), a Mobile Internet Device (MID), a wearable device, an electronic book reader (e-book reader), and the like. As another example, a wireless terminal may be a portable, pocket, hand-held, computer-included, or vehicle-mounted mobile device. As another example, a wireless terminal may be a mobile station (mobile station), an access point (access point), or a part of a User Equipment (UE).

For the network architecture shown in fig. 1, the following roaming scenarios are discussed in the 5G standard: (1) a home routing scenario; (2) a local breakout scenario.

Fig. 2A is a network architecture diagram of a home routing scenario, as shown in fig. 2A, the network architecture includes a network element of an HPLMN and a network element of a VPLMN, where the network element of the HPLMN includes an AUSF network element, a UDM network element, a home SMF network element (also may be referred to as an H-SMF network element), a home PCF network element (also may be referred to as an H-PCF network element), an AF network element, a home UPF network element (also may be referred to as an H-UPF network element), and a DN network element; the network elements of the VPLMN comprise a PCF network element (also called V-PCF network element) of a visited place, an SMF network element (also called V-SMF network element) of the visited place, an AMF network element, a RAN network element, a UPF network element (also called V-UPF network element) of the visited place and a terminal. With reference to the architecture shown in fig. 2A, the home routing means that when a PDU session is established, the V-SMF cannot process SM information in NAS signaling, and therefore, the PDU session needs to be established through a network element of the HPLMN.

The local breakout scenario may be further divided into two types, fig. 2B is a network architecture diagram of a first local breakout scenario, and as shown in fig. 2B, the network architecture includes a network element of the HPLMN and a network element of the VPLMN, where the network element of the HPLMN includes an AUSF network element, a UDM network element, an H-PCF network element, and an AF network element; the network elements of the VPLMN comprise a V-PCF network element, an SMF network element, an AMF network element, a RAN network element, a UPF network element, a DN network element and a terminal. Fig. 2C is a network architecture diagram of a second local breakout scenario, as shown in fig. 2C, the network architecture includes a network element of an HPLMN and a network element of a VPLMN, where the network element of the HPLMN includes an AUSF network element, a UDM network element, and an H-PCF network element; the network elements of the VPLMN comprise a V-PCF network element, an AF network element, an SMF network element, an AMF network element, a RAN network element, a UPF network element, a DN network element and a terminal.

With reference to the architectures shown in fig. 2B and fig. 2C, the local breakout means that when a PDU session is established, the V-SMF can process SM information in NAS signaling, so that the PDU session can be established through a network element of the VPLMN.

Consider that in a roaming scenario, some specific traffic must utilize the PDU session of the HPLMN to provide the PDU connection service. Therefore, when a PDU session is established, it is necessary to distinguish whether the PDU session to be established must be home routed. To solve this problem, in an implementation manner in the prior art, an AMF network element determines whether a PDU Session to be established must be subjected to home routing according to the number of Session Management (SM) containers (containers) carried in a Non-access transmission (NAS) message sent by a terminal, where information that can be processed by an SMF network element at a visited place is placed in one SM container, and information that must be processed by an SMF network element at the home place is separately placed in a newly added SM container. Specifically, if only one SM container is included in the NAS message sent by the terminal, it indicates that the PDU session to be established does not need to be subjected to home routing, and if two SM containers are included, it indicates that the PDU session to be established needs to be subjected to home routing. However, this approach results in a large number of SM containers, making the NAS message more complicated.

Based on the above, the present application provides a PDU session establishment method, which is used to effectively identify whether the PDU session to be established must be routed, thereby establishing the PDU session according to the identification result, and ensuring normal transmission of data service; and the problem that the NAS message is complex in the prior art is effectively avoided.

Example one

Fig. 3 is a schematic flowchart of a PDU session establishment method according to an embodiment of the present application, where as shown in fig. 3, the flowchart includes:

step 301, a terminal receives a first message, where the first message includes a roaming policy of the terminal;

step 302, the terminal determines whether the PDU session to be established is allowed to carry out local breakout or not according to the roaming strategy, and generates a PDU session establishment request; the PDU conversation establishing request comprises first indication information used for indicating whether the PDU conversation to be established allows local breakout or not;

step 303, the terminal sends the PDU session establishment request to the AMF network element;

step 304, the AMF network element receives a PDU session establishment request from the terminal;

step 305, the AMF network element generates a session management request according to the first indication information and sends the session management request.

As can be seen from the above, in the present application, the terminal determines, according to the roaming policy included in the first message, whether the PDU session to be established is allowed to be locally groomed, and generates a PDU session establishment request; because the PDU session establishment request comprises the first indication information used for indicating whether the PDU session to be established is allowed to be locally dredged or not, the AMF network element receiving the PDU session establishment request can generate the session management request according to the first indication information, and then the PDU session of the HPLMN or the PDU session of the VPLMN is established. Compared with the prior art that the PDU conversation to be established must be subjected to home routing according to SM container identification, the scheme in the application only uses one SM container, the number of the SM containers is not required to be increased, and the problem that NAS information is complex is effectively avoided.

Specifically, in step 301, the roaming policy of the terminal may be that the H-PCF network element allocates the terminal and sends the terminal to the terminal, or the roaming policy of the terminal may also be that the H-PCF network element allocates the terminal and sends the terminal to the V-PCF network element, and then the V-PCF network element sends the terminal to the terminal. The H-PCF network element may update the roaming policy of the terminal, for example, after the H-PCF determines that the subscription information of the user changes, the roaming policy of the terminal may be updated.

In a first possible implementation manner, the roaming policy of the terminal may include a correspondence between a type of the PDU session and a roaming identifier.

The PDU session type may be distinguished according to a terminal identifier and an application identifier (application identification), for example, the terminal identifier is a1, the application identifier is b1 represents a first type, the terminal identifier is a1, the application identifier is b2 represents a second type, and so on. The roaming flag may be represented in various forms of information, for example, using bits 0 and 1: the roaming identifier is 0, which indicates that local breakout is not allowed; the roaming flag is 1, indicating that local breakout is allowed. As shown in table 1, a part of the content of the first correspondence between the PDU session type and the roaming flag is shown.

Table 1: partial content indication of first correspondence of PDU session type and roaming flag

In table 1, the first type represented by the terminal identifier a1 and the application identifier b1 corresponds to the roaming identifier 0, that is, the PDU session belonging to the first type is not allowed to be locally groomed; the second type represented by the terminal identifier a1 and the application identifier b2 corresponds to roaming identifier 1, that is, the PDU session belonging to the second type allows local breakout.

It should be noted that, because the roaming policy received by the terminal is usually the roaming policy allocated by the H-PCF network element for the terminal according to the terminal identifier, the type of the PDU session may also be represented by only the application identifier in table 1.

Further, considering that the PDU session to be established is allowed to be locally thinned, the method includes two cases (respectively: the PDU session to be established is allowed to be locally thinned and needs HPLMN authorization; the PDU session to be established is allowed to be locally thinned and does not need HPLMN authorization), for further distinction, a roaming flag may also be set to two bits, where the first bit is used to indicate whether local thinning is allowed or not, and the second bit is used to indicate two cases where local thinning is allowed, for example, a roaming flag 00 (or a roaming flag 01) indicates that local thinning is not allowed; the roaming identifier is 11, which indicates that the PDU session to be established is allowed to be locally dredged and needs HPLMN authorization; the roaming flag is 10, indicating that the PDU session to be established is allowed to be conducted locally, and no HPLMN authorization is needed. As shown in table 2, it is a partial content of the second correspondence relationship between the PDU session type and the roaming flag.

Table 2: partial content indication of second correspondence of PDU session type and roaming flag

Type of PDU session	Roaming mark
		Application identification b1	00
Application identification b2	10
		Application identification b3	11
……	……
		The application identifier is bn	00

By adopting the mode in table 2, if the terminal determines that the first bit of the roaming identifier corresponding to the type of the PDU session to be established is 0, the terminal can directly determine that the PDU session to be established is not allowed to be locally dredged without judging the second bit, thereby saving processing resources; if the first bit is determined to be 1, the second bit can be further determined to distinguish between two situations allowing local breakout.

In this application, the type of the PDU session may also be distinguished by using a terminal identifier and a Data Network Name (DNN), that is, the application identifiers in table 1 and table 2 may be replaced by DNN, which is not described in detail.

It should be noted that, considering that the DNN includes an operator identifier (operator identification), the terminal may determine whether the PDU session to be established allows local breakout directly according to the operator identifier, and therefore, in the present application, the terminal identifier and the DNN may be used to distinguish the type of the PDU session when the DNN does not include the operator identifier, and further set the roaming policy.

In the first possible implementation manner, since the roaming policy of the terminal includes the corresponding relationship between the type of the PDU session and the roaming identifier, in step 302, the terminal may obtain the roaming identifier corresponding to the PDU session to be established according to the type of the PDU session to be established, and further determine whether the PDU session to be established allows local breakout.

In a second possible implementation manner, the roaming policy of the terminal may include a type of PDU session not allowed to perform local breakout, for example, if the roaming policy includes an application identifier b1 and an application identifier bn, it indicates that the PDU session belonging to the type represented by the application identifier b1 and the application identifier bn is not allowed to perform local breakout, and the PDU session belonging to another type allows local breakout.

In the second possible implementation manner, the roaming policy only needs to include the type of the PDU session that is not allowed to be locally groomed, so that the complexity of the roaming policy is effectively reduced. In step 302, the terminal may determine whether the type of the PDU session to be established is the same as the type included in the roaming policy, and if so, determine that the PDU session to be established is not allowed to perform local breakout, otherwise, determine that the PDU session to be established is allowed to perform local breakout.

As a variation of the second possible implementation manner, the roaming policy of the terminal may also include a type of PDU session allowed to perform local breakout, for example, if the roaming policy includes the application identifier b3, it indicates that the PDU session belonging to the type represented by the application identifier b3 is allowed to perform local breakout, and the PDU session belonging to another type is not allowed to perform local breakout.

As can be seen from the above, in the first possible implementation manner (when the roaming flag is represented by 0 and 1) and the second possible implementation manner, the terminal may distinguish whether the PDU session to be established is allowed to be locally groomed, and further, the terminal may generate the PDU session establishment request including the first indication information, at this time, since two cases of allowing the local grooming are not distinguished, the first indication information only indicates that the PDU session to be established is allowed to be locally groomed or not, for example, similar to the roaming flag, the first indication information may also be represented by 0 and 1, and the first indication information is 0 and indicates that the local grooming is not allowed; the first indication information is 1, which indicates that local breakout is allowed.

In this application, roaming scenarios specifically include three scenarios, that is: (1) local breakout, i.e. home routing scenario, is not allowed; (2) allowing local breakout and requiring HPLMN authorization; (3) local breakout is allowed and no HPLMN authorization is required. In order to clearly distinguish the three roaming scenarios, a first possible implementation manner (when the roaming flag is represented by two bits) may be preferably adopted, and at this time, the terminal may distinguish which roaming scenario the PDU session to be established belongs to, and further generate the PDU session establishment request including the first indication information. Similar to the roaming identifier, the first indication information may also be represented by two bits, where the first indication information is 00 or 01, and indicates that local breakout is not allowed; the first indication information is 10, which indicates that local breakout is allowed and HPLMN authorization is not needed; the first indication is 11, which indicates that local breakout is allowed and HPLMN authorization is required. This will be described as an example.

In step 304 and step 305, the AMF network element receives a PDU session establishment request from the terminal, and if the first indication information is 00 or 01, it is determined that such a scenario is a roaming scenario (1), that is, an home route, the AMF network element selects an SMF network element of a home location and an SMF network element of a visited location, generates a session management request, and sends the session management request to the SMF network element of the visited location, where the session management request includes identification information of the SMF network element of the home location.

If the first indication information is 11, determining that the scene is a roaming scene (2), that is, allowing local breakout and requiring HPLMN authorization, selecting an SMF network element of the visited place by the AMF network element, generating a session management request, and sending the session management request to the SMF network element of the visited place, where the session management request includes second indication information, and the second indication information is used to indicate that the PDU session to be established requires HPLMN authorization.

If the first indication information is 10, determining that the scene is a roaming scene (3), that is, allowing local breakout without HPLMN authorization, selecting an SMF network element of the visited place by the AMF network element, generating a session management request, and sending the session management request to the SMF network element of the visited place.

In summary, the present application provides a new idea for identifying different roaming scenarios, and specifically, a terminal determines whether a PDU session to be established is allowed to be locally groomed according to a roaming policy, and generates a PDU session establishment request, where the PDU session establishment request includes first indication information, so that after receiving the first indication information, an AMF network element can accurately and quickly identify different roaming scenarios, thereby triggering a procedure for establishing a PDU session of an HPLMN or a procedure for establishing a PDU session of a VPLMN.

The following describes the PDU session establishment procedure in the above three roaming scenarios with reference to the second to fourth embodiments.

Example two: PDU session establishment process under home routing scenario

Based on the network architecture shown in fig. 2A, fig. 4 is a schematic diagram of an establishment process of a PDU session in the second embodiment of the present application. As shown in fig. 4, includes:

step 401, a terminal receives a first message, where the first message includes a roaming policy of the terminal;

step 402, the terminal determines whether the PDU session to be established is allowed to carry out local breakout or not according to the roaming strategy, and generates a PDU session establishment request; the PDU session establishment request comprises first indication information; the first indication information indicates that the PDU conversation to be established does not allow local breakout, namely home routing is required;

step 403, the terminal sends the PDU session establishment request to the AMF network element;

step 404, the AMF network element receives a PDU session establishment request from the terminal;

step 405, the AMF network element selects an H-SMF network element and a V-SMF network element according to the first indication information, generates a session management request, and sends the session management request to the V-SMF network element, wherein the session management request comprises identification information of the H-SMF network element;

step 406, the V-SMF network element selects a UPF network element (i.e. a V-UPF network element) of the visited place, and sends an N4 session establishment request to the V-UPF network element;

step 407, the V-UPF network element sends an N4 session establishment response to the V-SMF network element;

step 408, the V-SMF network element sends a PDU session creation request to the H-SMF network element;

and step 409, the V-SMF network element receives the PDU session establishment request and establishes the PDU session of the HPLMN.

It should be noted that the PDU session to be established mentioned in this application is not allowed to be locally broken down (home routing is necessary), that is, the PDU session to be established needs to be established through the flow described in the above steps 403 to 409.

Example three: description of PDU Session establishment procedure in local breakout (and HPLMN authorization required) scenarios

Based on the network architecture shown in fig. 2B, fig. 5 is a schematic diagram of an establishment process of a PDU session in the third embodiment of the present application. As shown in fig. 5, includes:

step 501, a terminal receives a first message, wherein the first message comprises a roaming policy of the terminal;

step 502, the terminal determines whether the PDU session to be established is allowed to carry out local breakout or not according to the roaming strategy, and generates a PDU session establishment request; the PDU session establishment request comprises first indication information; the first indication information indicates that the PDU session to be established is allowed to be locally dredged and needs HPLMN authorization;

step 503, the terminal sends the PDU session establishment request to the AMF network element;

step 504, the AMF network element receives a PDU session establishment request from the terminal;

step 505, the AMF network element selects a V-SMF network element according to the first indication information, generates a session management request, and sends the session management request to the V-SMF network element, where the session management request includes second indication information, and the second indication information is used to indicate that a PDU session to be established needs HPLMN authorization;

step 506, the V-SMF network element selects a V-PCF network element and sends a PDU-CAN session establishment request to the V-PCF network element, wherein the PDU-CAN session establishment request comprises indication information for indicating that the PDU session to be established needs HPLMN authorization;

step 507, the V-PCF network element sends a PDU-CAN session authorization request to the H-PCF network element;

step 508, H-PCF network element returns PDU-CAN conversation authorizing response to V-PCF network element;

step 509, the V-PCF network element sends a PDU-CAN session establishment response to the V-SMF network element;

and step 510, the V-SMF network element receives the PDU-CAN session establishment response and establishes the PDU session of the VPLMN.

It should be noted that the PDU session to be established in this application allows local breakout (and requires HPLMN authorization), that is, the PDU session to be established can be established through the flow described in the above steps 503 to 510.

Example four: setting up PDU session in local breakout (without HPLMN authorization) scenario

Based on the network architecture shown in fig. 2C, fig. 6 is a schematic diagram of an establishment process of a PDU session in the fourth embodiment of the present application. As shown in fig. 6, includes:

601, a terminal receives a first message, wherein the first message comprises a roaming policy of the terminal;

step 602, the terminal determines whether the PDU session to be established is allowed to be locally groomed according to the roaming policy, and generates a PDU session establishment request; the PDU session establishment request comprises first indication information; the first indication information indicates that the PDU session to be established is allowed to be locally dredged without HPLMN authorization;

step 603, the terminal sends the PDU session establishment request to the AMF network element;

step 604, the AMF network element receives a PDU session establishment request from the terminal;

step 605, the AMF network element selects the V-SMF network element according to the first indication information, generates a session management request, and sends the session management request to the V-SMF network element;

step 606, after the V-SMF network element receives the session management request, the PDU session of the VPLMN is established.

It should be noted that the PDU session to be established in this application allows local breakout (and does not need HPLMN authorization), that is, the PDU session to be established can be established through the flow described in the above steps 603 to 606.

Fig. 7 is a schematic structural diagram of a terminal according to an embodiment of the present invention. As shown in fig. 7, the terminal 700 includes: a transmitter 701a, a receiver 701b, a processor 702, a memory 703 and a bus system 704;

the memory 703 is used for storing programs. In particular, the program may include program code including computer operating instructions. The memory 703 may be a Random Access Memory (RAM) or a non-volatile memory (non-volatile memory), such as at least one disk memory. Only one memory is shown in the figure, but of course, the memory may be provided in plural numbers as necessary. The memory 703 may also be memory in the processor 702.

The memory 703 stores elements, executable modules or data structures, or a subset or an expanded set thereof:

and (3) operating instructions: including various operational instructions for performing various operations.

Operating the system: including various system programs for implementing various basic services and for handling hardware-based tasks.

Processor 702 controls the operation of terminal 700, and processor 702 may also be referred to as a CPU (Central processing Unit). In a particular application, the various components of the terminal 700 are coupled together by a bus system 704, where the bus system 704 may include a power bus, a control bus, a status signal bus, and the like, in addition to a data bus. For clarity of illustration, however, the various buses are designated in the figure as the bus system 704. For ease of illustration, it is only schematically drawn in fig. 7.

The methods disclosed in the embodiments of the present application may be implemented in the processor 702 or implemented by the processor 702. The processor 702 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 702. The processor 702 described above may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 703, and the processor 702 reads the information in the memory 703 and executes the method steps executed by the terminal in combination with the hardware.

Fig. 8 is a schematic structural diagram of an AMF network element according to an embodiment of the present invention. As shown in fig. 8, the AMF network element 800 includes: a transmitter 801a, a receiver 801b, a processor 802, a memory 803, and a bus system 804;

the memory 803 is used for storing programs. In particular, the program may include program code including computer operating instructions. The memory 803 may be a Random Access Memory (RAM) or a non-volatile memory (non-volatile memory), such as at least one disk memory. Only one memory is shown in the figure, but of course, the memory may be provided in plural numbers as necessary. The memory 803 may also be memory within the processor 802.

The memory 803 stores the following elements, executable modules or data structures, or a subset thereof, or an expanded set thereof:

The processor 802 controls the operation of the AMF network element 800, and the processor 802 may also be referred to as a CPU (central processing Unit). In a specific application, the various components of the AMF network element 800 are coupled together by a bus system 804, wherein the bus system 804 may include a power bus, a control bus, a status signal bus, etc., in addition to a data bus. For clarity of illustration, however, the various buses are designated in the figure as the bus system 804. For ease of illustration, it is only schematically drawn in fig. 8.

The method disclosed in the embodiments of the present application can be applied to the processor 802, or implemented by the processor 802. The processor 802 may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware or instructions in the form of software in the processor 802. The processor 802 described above may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in the memory 803 and the processor 802 reads the information in the memory 803 and in combination with its hardware performs the above method steps performed by the AMF network element.

Based on the same inventive concept, the present application further provides a communication entity 900, as shown in fig. 9, which includes a processing unit 901 and a transceiver unit 902, and is configured to execute the method executed by the terminal in any of the embodiments described above. The communication entity 900 may be a terminal.

Optionally, the transceiver 902 is configured to perform receiving a first message, where the first message includes a roaming policy of the terminal;

the processing unit 901 is configured to determine whether a PDU session to be established is allowed to perform local breakout according to the roaming policy, and generate a PDU session establishment request; the PDU conversation establishing request comprises first indication information used for indicating whether the PDU conversation to be established allows local breakout or not;

the transceiving unit 902 is further configured to perform sending the PDU session establishment request to an access and mobility management function, AMF, network element.

Optionally, the roaming policy includes a type of PDU session not allowed for local breakout;

the processing unit 901 is specifically configured to:

Optionally, the roaming policy includes a correspondence between a type of the PDU session and a roaming identifier; the roaming identifier is used for indicating whether the PDU session belonging to the type corresponding to the roaming identifier allows local breakout;

the processing unit 901 is specifically configured to:

Optionally, the allowing of local breakout for the PDU session to be established includes:

Based on the same inventive concept, the present application further provides a communication entity 1000, as shown in fig. 10, including a processing unit 1001 and a transceiver unit 1002, which can be used to execute the method executed by the terminal in any of the above embodiments. The communication entity 1000 may be an AMF network element.

Optionally, the transceiver 1002 is configured to execute receiving a PDU session establishment request from a terminal, where the PDU session establishment request includes first indication information used for indicating whether a PDU session to be established is allowed to be locally groomed;

the processing unit 1001 is configured to execute generating a session management request according to the first indication information;

the transceiver 1002 is further configured to execute sending the session management request, where the session management request is used to request to establish the PDU session.

Optionally, when the first indication information indicates that the PDU session to be established is not allowed to be locally groomed, the session management request includes identification information of an SMF network element of a home location selected by the AMF network element, and the session management request is used to request establishment of a PDU session of an HPLMN.

Optionally, when the first indication information indicates that the to-be-established PDU session is allowed to be locally groomed, the session management request is used to request to establish a PDU session of a VPLMN.

Optionally, when the first indication information indicates that the to-be-established PDU session is allowed to be locally groomed and needs to be authorized by the HPLMN, the session management request includes second indication information for indicating that the to-be-established PDU session needs to be authorized by the HPLMN, and the session management request is used for requesting to perform authorization by the HPLMN and establish a PDU session of the VPLMN.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions described in accordance with the present application are generated, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic cable, Digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that a computer can store or a data storage device including a server, a data center, etc. integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Those skilled in the art will also appreciate that the various illustrative logical blocks and steps (step) set forth herein may be implemented in electronic hardware, computer software, or combinations of both. Whether such functionality is implemented as hardware or software depends upon the particular application and design requirements of the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The various illustrative logical units and circuits described herein may be implemented or operated by a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.

The steps of a method or algorithm described in this application may be embodied directly in hardware, in a software element executed by a processor, or in a combination of the two. The software unit may be stored in a Random-access Memory (RAM), a flash Memory, a Read-Only Memory (ROM), an Erasable Programmable Read-Only Memory (EPROM), a register, a hard disk, a removable disk, a Compact Disc Read-Only Memory (CD-ROM), or any other storage medium in the art. For example, a storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may be located in a terminal device or a network device. In the alternative, the processor and the storage medium may reside as discrete components in a terminal device or network device.

In one or more exemplary designs, the functions described herein may be implemented in hardware, software, firmware, or any combination of the three. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media that facilitate transfer of a computer program from one place to another. Storage media may be any available media that can be accessed by a general purpose or special purpose computer. For example, such computer-readable media can include, but is not limited to, RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store program code in the form of instructions or data structures and which can be read by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Additionally, any connection is properly termed a computer-readable medium, and, thus, is included if the software is transmitted from a website, server, or other remote source over a coaxial cable, fiber optic computer, twisted pair, Digital Subscriber Line (DSL), or wirelessly, e.g., infrared, radio, and microwave. The disk (disk) and Disc (Disc) include compact Disc, laser Disc, optical Disc, Digital Versatile Disc (DVD), floppy disk and blu-ray Disc, where the disk usually reproduces data magnetically, and the Disc usually reproduces data optically with laser. Combinations of the above may also be included in the computer-readable medium.

Those skilled in the art will recognize that in one or more of the examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-mentioned embodiments, objects, technical solutions and advantages of the present application are further described in detail, it should be understood that the above-mentioned embodiments are only examples of the present application, and are not intended to limit the scope of the present application, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present application should be included in the scope of the present application. The foregoing description of the specification may enable any person skilled in the art to make or use the teachings of the present application, and any modifications based on the disclosed teachings should be considered as obvious in the art, and the general principles described herein may be applied to other variations without departing from the spirit or scope of the present application. Thus, the disclosure is not intended to be limited to the embodiments and designs described, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A Protocol Data Unit (PDU) session establishment method, the method comprising:

the terminal sends the PDU session establishment request to an access and mobility management function (AMF) network element;

wherein the allowing of the local breakout for the to-be-established PDU session comprises: the PDU session to be established allows local breakout and requires home public land mobile network HPLMN authorization; or, the PDU session to be established allows local breakout without HPLMN authorization.

2. The method of claim 1, wherein the roaming policy comprises a type of PDU session not allowed for local breakout;

if the type of the PDU session to be established belongs to the type of the PDU session not allowed to be locally thinned and included in the roaming strategy, the terminal determines that the PDU session to be established is not allowed to be locally thinned.

3. The method of claim 1, wherein the roaming policy comprises a correspondence between a type of PDU session and a roaming flag; the roaming identifier is used for indicating whether the PDU session belonging to the type corresponding to the roaming identifier allows local breakout;

4. A PDU session establishment method, the method comprising:

the AMF network element generates a session management request according to the first indication information and sends the session management request, wherein the session management request is used for requesting to establish the PDU session;

when the first indication information indicates that the PDU session to be established is allowed to be locally dredged and needs to be authorized by the HPLMN, the session management request comprises second indication information used for indicating that the PDU session to be established needs to be authorized by the HPLMN, and the session management request is used for requesting to authorize by the HPLMN and establishing the PDU session of a Visited Public Land Mobile Network (VPLMN).

5. The method of claim 4, wherein:

when the first indication information indicates that the PDU session to be established is not allowed to be locally groomed, the session management request includes identification information of the SMF network element of the home location selected by the AMF network element, and the session management request is used for requesting establishment of a PDU session of the HPLMN.

6. The method of claim 4, wherein:

and when the first indication information indicates that the PDU session to be established is allowed to be subjected to local breakout, the session management request is used for requesting to establish the PDU session of the VPLMN.

7. A communication entity, characterized in that the communication entity comprises a processor coupled with at least one memory; the processor for executing a computer program or instructions stored in the at least one memory, the computer program or instructions, when executed, causing the method of any of claims 1 to 3 to be performed.

8. A communication entity, characterized in that the communication entity comprises a processor coupled with at least one memory; the processor configured to execute a computer program or instructions stored in the at least one memory, the computer program or instructions when executed causing the method of any of claims 4 to 6 to be performed.