Method and apparatus for session service management - Patents.com

Abstract

Various embodiments of the present disclosure provide methods and apparatus for session service management. The method performed by a first session management function includes determining first N4 information related to a user plane function (UPF). The first N4 information includes an identifier of the UPF. The method further includes sending a first message including the first N4 information to a second session management function.

Description

[Technical field]

[0001] The present disclosure relates generally to communication networks, and more particularly to a method and apparatus for multicast communication. [Background technology]

[0002] This section introduces aspects that may facilitate a better understanding of the present disclosure. As such, the statements in this section are to be read in this light and not as admissions of prior art or non-prior art.

[0003] Communication service providers and network operators are constantly faced with the challenge of delivering value and convenience to consumers (e.g., by providing compelling network services and performance). With the rapid development of networking and communication technologies, wireless communication networks, such as Long Term Evolution (LTE) / fourth generation (4G) networks or New Radio (NR) / fifth generation (5G) networks, are expected to achieve high traffic capacity and end-user data rates. The 3rd generation partnership project (3GPP) is developing various network function services for various communication networks to meet the diverse requirements of new services across diverse industries.

[0004] A single Protocol Data Unit (PDU) session using multiple PDU Session Anchors (PSAs) is specified in 3GPP TS 23.501 V16.7.0, the disclosure of which is incorporated herein by reference in its entirety. As defined in clause 5.6.9.2.3 of 3GPP TS 23.501 V16.7.0, to support selective traffic routing to a DN (data network) or to support SSC (Session and Service Continuity) mode 3, a Session Management Function (SMF) can control the data path of a PDU session such that the PDU session can simultaneously serve multiple N6 interfaces. A UPF terminating each of these interfaces is said to support the PDU Session Anchor function. Each PDU Session Anchor supporting a PDU session provides a different access to the same DN. Furthermore, the PDU session anchor assigned at the PDU (User Plane Function) session establishment is associated with the SSC mode of the PDU session, while additional (one or more) PDU session anchors assigned within the same PDU session, e.g. for selective traffic routing to DNs, are independent of the SSC mode of the PDU session. If the SMF is provided with a PCC (Policy and Charging Control) rule that includes AF (Application Function) impacted traffic steering enforcement control information defined in clause 6.3.1 of 3GPP TS 23.503 V16.7.0, the SMF can decide whether to apply traffic routing (using a UL (Uplink) Classifier function or IPv6 (Internet Protocol version 6) multihoming) based on the (one or more) DNAI (DN Access Identifiers) included in the PCC rule.

[0005] Clause 5.34.6 of 3GPP TS 23.501 V16.7.0 describes the interaction between the I-SMF (Intermediate Session Management Function) and the SMF for the support of traffic offload by UPF controlled by the I-SMF. When the I-SMF is inserted into a PDU session, e.g. during PDU session establishment or due to UE mobility, the I-SMF can provide the SMF with the DNAI list it supports. Based on the DNAI list information received from the I-SMF, the SMF can provide the target DNAI(s) for this PDU session for local traffic steering to the I-SMF, e.g. immediately or when new, updated or removed PCC rule(s) are received. The target DNAI(s) are derived from the PCC rule. The I-SMF is responsible for the insertion, modification and removal of UPF to ensure local traffic steering. Based on the target DNAI(s) for the PDU session for local traffic steering and the UE (User Equipment) location, the I-SMF determines which DNAI(s) should be selected, and based on the selected DNAI, selects (one or more) UPFs acting as UL CL (Classifier) / BP (Branch Point) and / or PDU session anchors, and inserts these UPF(s) into the data path of the PDU session.

[0006] Clause 5.34.6.2 of 3GPP TS 23.501 V16.7.0 describes the N4 information sent from the SMF to the I-SMF for local traffic offload. The SMF generates the N4 information for local traffic offload based on the available DNAI(s) indicated by the I-SMF, the PCC rules associated with these DNAI(s) and the charging requirements. This N4 information is sent from the SMF to the I-SMF after insertion / update / deletion of UL CL / branching points, and the I-SMF uses this N4 information to derive the rules installed in the UPF controlled by the I-SMF. The N4 information for local traffic offload corresponds to the rules and parameters defined in clause 5.8.2.11 of 3GPP TS 23.501 V16.7.0. It includes identifiers that allow the SMF to later modify or delete these rules. The N4 information for local traffic offload is generated by the SMF without knowledge of the number of local UPF(s) actually used by the I-SMF. The SMF indicates whether the rule in the N4 information is enforced at the UL CL / branching point or at the local PSA. If the rule applies to a local PSA, the N4 information includes the associated DNAI. The I-SMF generates the appropriate rules for the UPF(s) based on the N4 information received from the SMF. The SMF is not aware of whether the I-SMF controls one or multiple PSAs.

[0007] Figure 1 shows a flow chart of PDU session anchoring and adding a branching point or UL CL controlled by the I-SMF. Figure 1 is the same as Figure 4.23.9.1-1 of 3GPP TS 23.502 V16.7.1, the disclosure of which is incorporated herein by reference in its entirety. The steps of Figure 1 are described in section 4.23.9.1 of 3GPP TS 23.502 V16.7.1, and the description thereof is omitted here for brevity.

[0008] In step 2, the I-SMF uses the list of eligible DNAI(s) for this PDU session received from the SMF to decide to establish a new PDU session anchor, e.g. due to UE mobility. The I-SMF selects a UPF and establishes a new PDU Session Anchor 2 (PSA2) for the PDU session using N4.

[0009] In step 4, the I-SMF invokes a Nsmf_PDUSession_Update Request (UL CL or branch point insertion indication, IPv6 prefix @ PSA2, (one or more) DNAIs supported by PSA2) to the SMF. Multiple local PSAs (i.e. PSAs 2) may be inserted at once, each corresponding to a DNAI and / or IPv6 prefix in case of multihoming.

[0010] Figure 2 shows a flow chart of PDU session anchoring and branching point or UL CL removal controlled by I-SMF. Figure 2 is the same as Figure 4.23.9.2-1 of 3GPP TS 23.502 V16.7.1. The steps in Figure 2 are described in clause 4.23.9.2 of 3GPP TS 23.502 V16.7.1 and are omitted here for brevity.

[0011] In step 3, the I-SMF invokes an Nsmf_PDUSession_Update Request (Traffic Offload Deletion Indication, Delete IPv6 Prefix @PSA2, DNAI associated with PSA2) to the SMF. Multiple local PSAs may be deleted, in which case the I-SMF provides each local PSA to be deleted, the associated DNAI, and the IPv6 prefix in case of multihoming.

[0012] Figure 3 shows a flow chart of the branching point or PDU session anchor change for UL CL controlled by I-SMF. Figure 3 is the same as Figure 4.23.9.3-1 of 3GPP TS 23.502 V16.7.1. The steps in Figure 3 are described in clause 4.23.9.3 of 3GPP TS 23.502 V16.7.1 and are omitted here for brevity.

[0013] In step 2, the I-SMF decides to establish a new PDU session anchor and release the existing PDU session anchor, e.g. due to UE mobility. The I-SMF selects a UPF and establishes a new PDU session anchor 2 for the PDU session using N4.

[0014] In step 3, the I-SMF invokes an Nsmf_PDUSession_Update Request (Traffic Offload Change Indication, (Newly assigned IPv6 prefix @PSA2, DNAI(s) supported by PSA2), (Deletion of IPv6 prefix @PSA0, DNAI supported by PSA0)) to the SMF.

[0015] 3GPP TS 29.502 V16.6.0, the disclosure of which is incorporated herein by reference in its entirety, describes the detailed information of PSA information (psaInfo). An example of how to fill in psaInfo is shown below. Nsmf_PDUSession_Update Request (I-SMF initiated) + HsmfUpdateData + psaInfo - pasInd: PSA_INSERTED / PSA_REMOVED - dnaiList: dnaiList supported by the PSA2 to be inserted - psaUpfId: PSA2 NfInstanceId

[0016] Table 1 shows the definition of type HsmfUpdateData. Table 1 is a truncated version of Table 6.1.6.2.11-1 of 3GPP TS 29.502 V16.6.0. [Table 1]

[0017] Table 2 shows the definition of type PsaInformation. Table 2 is a truncated version of Table 6.1.6.2.41 of 3GPP TS 29.502 V16.6.0. [Table 2]

[0018] Table 3 shows the type N4 information The definition of is shown in Table 3. Table 3 is an abbreviated version of Table 6.1.6.2.41 of 3GPP TS 29.502 V16.6.0. [Table 3] Summary of the Invention

[0019] This Summary is intended to introduce in a simplified form certain concepts that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

[0020] FIG. 4 illustrates an example architecture of the use of UL classifier / IPv6 multihoming for a PDU session controlled by an I-SMF with multiple local PSAs according to an embodiment of the present disclosure.

[0021] If multiple local PSAs (e.g. PSA2 and PSA3) are inserted at one time, for example, then for each local PSA, the list of DNAIs supported by each local PSA is provisioned from the I-SMF to the SMF, and psaUpfid is also provisioned from the I-SMF to the SMF. The psaUpfid is used at the N40 interface for billing purposes if a quota is allowed for each UPF. RuU It may correspond to the NfInstanceId of the PF (see section 5.2.1.10 of 3GPP TS 32.255 V17.0.0, the disclosure of which is incorporated herein by reference in its entirety). The problem is that when the I-SMF needs to send N4 information (e.g., reporting traffic usage) to the SMF for traffic offloaded on multiple PSAs controlled by the I-SMF, it needs to indicate which PSA the N4 information (e.g., reporting traffic usage) corresponds to, but all PFCP (Packet Forwarding Control Plane) session messages (e.g., PFCP Session Modification Request / Response, PFCP Session Deletion Request / Response, PFCP Session Report Request / Response) carried on the N16a interface do not have the corresponding UPF Identifier information. Also, currently, the only parameter that matches the psaUpfId information is 'n4DnaiInfo'. See Table 3 above. When an I-SMF controls multiple local PSAs, there may be a problem in how to identify which PSA the N4 information corresponds to, if the dnaiLists of multiple PSAs have at least one overlapping value. For example, the SMF may receive two n4infos with n4DnaiInfo set to 'b', while it already has information on PSA2 dnaiList (a, b, c) and PSA3 dnaiList (b, c, d) based on a previously received (I-SMF initiated) Nsmf_PDUSession_Update Request. In this case, the SMF cannot identify which PSA the n4Info corresponds to.

[0022] Conversely, if an SMF needs to send N4 information to the I-SMF to control traffic offloaded to PSA2 or PSA3, or both PSA2 and PSA3, that are controlled by the I-SMF, the I-SMF cannot identify which PSA the N4 information with n4DnaiInfo 'b' corresponds to, because both PSA2 and PSA3 provide the same n4DnaiInfo 'b'.

[0023] Note that although Figure 4 shows only two UPFs supporting the same DNAI 'b', there may be more than two UPFs supporting at least one of the same DNAIs to achieve load balancing and node redundancy.

[0024] To overcome or mitigate at least one of the above-mentioned problems or other problems, embodiments of the present disclosure propose an improved solution for session service management.

[0025] According to a first aspect of the present disclosure, there is provided a method performed by a first session management function. The method includes determining first N4 information related to a user plane function (UPF). The first N4 information includes an identifier of the UPF. The method further includes sending a first message including the first N4 information to a second session management function.

[0026] In one embodiment, determining the first N4 information for the UPF comprises receiving a second message from the UPF including second N4 information for the UPF, where the second N4 information does not include the identifier of the UPF, and adding the identifier of the UPF to the second N4 information to generate the first N4 information.

[0027] In one embodiment, determining the first N4 information for the UPF comprises receiving a third message from the UPF including third N4 information for the UPF, wherein the third N4 information includes the identifier of the UPF, and using the third N4 information as the first N4 information.

[0028] In one embodiment, the method further comprises receiving a fourth message from the second session management function including fourth N4 information related to the UPF, the fourth N4 information including the identifier of the UPF, and sending the fourth message to the UPF based on the identifier of the UPF.

[0029] In one embodiment, the first session management function comprises an intermediate session management function.

[0030] In one embodiment, the N4 information regarding the UPF is included in at least one of a session release message, a session update message, a session modify message, or a session report message.

[0031] In one embodiment, the role of the N4 information is: The N4 information by a session management function to report traffic usage for traffic offloaded by the UPF; The N4 information Used by the session management function to control traffic offloaded by the UPF of Contains at least one.

[0032] In one embodiment, the UPF comprises a Protocol Data Unit Session Anchor (PSA) UPF.

[0033] According to a second aspect of the present disclosure, there is provided a method performed by a second session management function, the method comprising receiving a first message from a first session management function, the first message comprising first N4 information related to a user plane function (UPF), the first N4 information comprising an identifier of the UPF, the method further comprising processing the first message based on the identifier of the UPF.

[0034] In one embodiment, the method further comprises sending a fourth message to the first session management function including fourth N4 information regarding the UPF, the fourth N4 information including the identifier of the UPF.

[0035] According to a third aspect of the present disclosure, a first session management function is provided. The first session management function has a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The first session management function is operable to determine first N4 information relating to a User Plane Function (UPF). The first N4 information includes an identifier of the UPF. The first session management function is further operable to send a first message including the first N4 information to a second session management function.

[0036] According to a fourth aspect of the present disclosure, a second session management function is provided. The second session management function has a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The second session management function is operable to receive a first message from a first session management function, the first message including first N4 information related to a User Plane Function (UPF), the first N4 information including an identifier of the UPF. The second session management function is further operable to process the first message based on the identifier of the UPF.

[0037] According to a fifth aspect of the present disclosure, a first session management function is provided. The first session management function includes a determining module and a first sending module. The determining module may be configured to determine first N4 information related to a User Plane Function (UPF). The first N4 information includes an identifier of the UPF. The first sending module may be configured to send a first message including the first N4 information to a second session management function.

[0038] In an embodiment, the first session management function may further comprise a receiving module configured to receive a fourth message from the second session management function including fourth N4 information related to the UPF, the fourth N4 information including the identifier of the UPF.

[0039] In one embodiment, the first session management function may further include a second sending module configured to send the fourth message to the UPF based on the identifier of the UPF.

[0040] According to a sixth aspect of the present disclosure, a second session management function is provided. The second session management function includes a receiving module and a processing module. The receiving module may be configured to receive a first message from a first session management function, the first message including first N4 information related to a User Plane Function (UPF). The first N4 information includes an identifier of the UPF. The processing module may be configured to process the first message based on the identifier of the UPF.

[0041] In an embodiment, the second session management function may further comprise a sending module configured to send a fourth message to the first session management function including fourth N4 information related to the UPF, the fourth N4 information including the identifier of the UPF.

[0042] According to a seventh aspect of the present disclosure, there is provided a computer program product having instructions which, when executed by at least one processor, cause the at least one processor to perform a method according to any one of the first to sixth aspects.

[0043] According to an eighth aspect of the present disclosure, there is provided a computer-readable storage medium storing instructions which, when executed by at least one processor, cause the at least one processor to perform a method according to any one of the first and second aspects.

[0044] The embodiments of the present disclosure provide many advantages, some of which are listed below. In some embodiments of the present disclosure, the proposed solution allows the session management functions, such as the SMF and I-SMF, to identify which UPF (such as the PSA UPF) the N4 information corresponds to when multiple local UPFs (such as the PSA UPF) are inserted and controlled by the session management functions. In some embodiments of the present disclosure, the proposed solution can save the interaction between the session management functions, such as the I-SMF, and the UPFs, such as the PSA UPF. In some embodiments of the present disclosure, the proposed solution can simplify the handling of the N16a N4 information. The embodiments of the present disclosure are not limited to the above-mentioned features and advantages. The skilled person will recognize additional features and advantages from reading the following detailed description. [Brief description of the drawings]

[0045] The above and other aspects, features, and advantages of various embodiments of the present disclosure will become more fully apparent from the following detailed description, taken in conjunction with the accompanying drawings, in which like reference numbers or letters are used to indicate similar or equivalent elements, and in which the drawings are illustrated for ease of understanding of the embodiments of the present disclosure and are not necessarily drawn to scale.

[0046] [Figure 1]FIG. 1 is a flow chart of PDU session anchoring and branching point or addition of UL CL controlled by I-SMF.

[0047] [Diagram 2] FIG. 2 is a flow chart of PDU session anchoring and branching point or UL CL deletion controlled by I-SMF.

[0048] [Diagram 3] FIG. 3 is a flowchart of a branching point or PDU session anchor change for UL CL controlled by the I-SMF.

[0049] [Figure 4] FIG. 4 illustrates an example architecture of the use of UL classifier / IPv6 multihoming for a PDU session controlled by an I-SMF with multiple local PSAs according to an embodiment of the present disclosure.

[0050] [Diagram 5] FIG. 5 is a schematic diagram illustrating a high level architecture in a fifth generation network, according to an embodiment of the present disclosure.

[0051] [Figure 6] FIG. 6 is a flow chart of a method according to an embodiment of the present disclosure.

[0052] [Figure 7] FIG. 7 is a flowchart of a method according to another embodiment of the present disclosure.

[0053] [Figure 8] FIG. 8 is a flow chart of a method according to an embodiment of the present disclosure.

[0054] [Figure 9] FIG. 9 is a block diagram illustrating an apparatus suitable for implementing some embodiments of the present disclosure.

[0055] [Figure 10] FIG. 10 is a block diagram illustrating a first session management function according to an embodiment of the present disclosure.

[0056] [Figure 11] FIG. 11 is a block diagram illustrating a second session management function according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0057] Hereinafter, the embodiments of the present invention will be described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and consequently practice the present disclosure, and are not intended to imply any limitations on the scope of the present disclosure. Throughout this specification, references to features, advantages, or similar words do not imply that all of the features and advantages that may be realized in the present disclosure should or are present in any single embodiment of the present disclosure. Rather, words referring to features and advantages are understood to mean that the particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present disclosure. Furthermore, the features, advantages, and characteristics described in the present disclosure can be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages that may not be present in any embodiment of the present disclosure may be recognized in a particular embodiment.

[0058] As used in this disclosure, the term "network" refers to a network conforming to any suitable communications standard, such as New Radio (NR), Long Term Evolution (LTE), LTE Advanced, Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Address (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. A CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), which includes WCDMA and other variants of CDMA. A TDMA network may implement a radio technology such as Globals System for Mobile Communications (GSM). The OFDMA network may implement wireless technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, ad-hoc networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" may be used interchangeably. Furthermore, communication between two devices in the network may be performed according to any suitable communication protocol, including, but not limited to, communication protocols defined by a standardization organization such as 3GPP. For example, the communication protocol may include first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols, and / or any other protocols currently known or developed in the future.

[0059] The term "Network Function (NF)" refers to any suitable Network Function (NF) that may be implemented in a (physical or virtual) network entity of a communication network. For example, a network function may be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, for example on a cloud infrastructure. For example, a 5G system (5GS) may have multiple NFs, such as AMF (Access and Mobility Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management Function), PCF (Policy Control Function), AF (Application Function), NEF (Network Exposure Function), UPF (User Plane Function), and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Proxy), NWDAF (Network Data Analysis Function), NSSF (Network Slice Selection Function), NSSAAF (Network Slice Specific Authentication and Authorization Function). For example, a 4G system (such as LTE) may include multiple NFs, such as a Mobile Management Entity (MME), a Home Subscriber Server (HSS), a Policy and Charging Rules Function (PCRF), a Packet Data Network Gateway (PGW), a PGW Control Plane (PGW-C or P-GW-C), a Serving Gateway (SGW), a SGW Control Plane (SGW-C), an E-UTRAN Node B (eNB), etc. In other embodiments, the network functions may have different types of NFs depending on, for example, the particular network.

[0060] The term "terminal equipment" refers to any end equipment capable of accessing and receiving services from a communications network. By way of example and not limitation, terminal equipment refers to a mobile terminal, user equipment (UE), or other suitable device. A UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS), or an access terminal (AT). Terminal equipment may include, but is not limited to, portable computers, imaging terminal equipment such as digital cameras, gaming terminal equipment, music storage and playback equipment, mobile phones, cellular phones, smartphones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, wearable terminal equipment, in-vehicle wireless terminal equipment, wireless endpoints, mobile stations, laptop embedded equipment (LEE), laptop mounted equipment (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), and the like. In the following description, the terms "terminal equipment", "terminal", "user equipment", and "UE" may be used interchangeably. As an example, a terminal device may represent a UE configured to communicate according to one or more communications standards promulgated by 3GPP (3rd Generation Partnership Project), such as the LTE or NR standards of 3GPP. As used in this disclosure, "user equipment" or "UE" may not necessarily have a "user" in the sense of a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to transmit and / or receive information without direct human involvement. For example, a terminal device may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the communication network. Alternatively, a UE may represent equipment intended for sale to or operation by a human user, but not initially associated with a particular human user.

[0061] As yet another example, in an Internet of Things (IoT) scenario, a terminal device may represent a machine or other equipment that performs monitoring and / or measurements, etc., and transmits results of such monitoring and / or measurements, etc., to another terminal device and / or network device. The terminal device may in this case be a machine-to-machine (M2M) device, which may be referred to as a machine-type communication (MTC) device in the context of 3GPP. As one specific example, the terminal device may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Examples of such machines or equipment are sensors, metering devices such as power meters, industrial machines, or home or personal appliances, such as refrigerators, televisions, personal wearables (watches, etc.). In other scenarios, the terminal device may represent a vehicle or other equipment that can monitor and / or report its operating status or other equipment related to its operation.

[0062] References in this disclosure to "one embodiment," "an embodiment," "an exemplary embodiment," and the like indicate that the embodiment being described may include a particular feature, structure, or characteristic, but not all embodiments need to include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is implied that it is within the knowledge of one of ordinary skill in the art to use such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0063] Although terms such as "first", "second" and the like may be used in the present disclosure to describe various elements, it should be understood that these elements should not be limited by these terms. These terms are used only to distinguish one element from another element. For example, within the scope of the exemplary embodiment, a first element can be referred to as a second element, and similarly, a second element can be referred to as a first element. In the present disclosure, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0064] As used in this disclosure, the phrase "at least one of A and B" or "at least one of A or B" should be understood to mean "A only, B only, or both A and B." The phrase "A and / or B" should be understood to mean "A only, B only, or both A and B."

[0065] The terms used in this disclosure are for the purpose of describing particular embodiments only and are not intended to limit the exemplary embodiments. In this disclosure, the singular forms "a" and "an" are intended to include the plural forms unless the context clearly indicates otherwise. In this disclosure, the terms "comprises," "comprising," "has," "having," "includes," and / or "including" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence of one or more other features, elements, components, and / or combinations thereof.

[0066] It should be noted that these terms used in this disclosure are used only for ease of description and differentiation of nodes, devices, or networks, etc. As the technology develops, other terms having similar / same meanings may also be used.

[0067] In the following description and claims, unless otherwise defined, all technical and scientific terms used in this disclosure have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0068] Although the subject matter described in this disclosure may be implemented in any suitable type of system using any suitable components, the embodiments disclosed in this disclosure are described with respect to a communication system conforming to the exemplary system architecture shown in FIG. 5. For simplicity, the system architecture of FIG. 5 depicts only some exemplary elements. In practice, the communication system may further include any additional elements suitable for supporting communications between terminal devices, or between wireless devices and other communication devices (such as landlines, service providers, or other network nodes or terminal devices). A communication system may provide communications and various types of services to one or more terminal devices and facilitate terminal device access to and / or utilization of services provided by or using the communication system.

[0069] FIG. 5 is a schematic diagram illustrating a high-level architecture in a fifth generation network according to an embodiment of the present disclosure. For example, the fifth generation network may be a 5GS. The architecture in FIG. 5 is the same as FIG. 5.34.4-1 in 3GPP TS 23.501 V16.7.0, the disclosure of which is incorporated herein by reference in its entirety. The system architecture in FIG. 5 may have several exemplary elements, such as AMF, DN (Data Network), SMF, I-SMF UPF, UE, and AN (Access Network).

[0070] 5 also illustrates several reference points, such as N1, N2, N3, N4, N6, N1, N16a, and N9, that can support interactions between NF services in multiple NFs. For example, these reference points can be realized through corresponding NF service-based interfaces and by specifying several NF service consumers and providers and their interactions to perform specific system procedures.

[0071] The various NFs shown in Figure 5 may be responsible for functions such as session management, access and mobility management, user plane functions, UL CL, etc. The AMF, SMF, I-SMF, and UPF may include functions such as those defined in 3GPP TS 23.501 V16.7.0, clause 6.2.

[0072] In one embodiment, the subject matter described in this disclosure may be implemented in an architecture such as that described in section 5.34.2 of 3GPP TS23.501 V16.7.0.

[0073] Although only one PSA UPF 2 is shown in FIG. 5, in other embodiments there may be more than one PSA UPF 2 controlled by an I-SMF.

[0074] FIG. 6 is a flow chart of a method according to an embodiment of the present disclosure. The method may be performed by an apparatus implemented in / as the first session management function or an apparatus communicatively connected to the first session management function. Thus, the apparatus may provide means or modules for accomplishing various parts of the method 600, as well as means or modules for accomplishing other processes in cooperation with other components. The first session management function may be any suitable entity or node capable of implementing a session management function. For example, the first session management function may be an SMF or an I-SMF.

[0075] At block 602, the first session management function may determine first N4 information related to a user plane function (UPF). The first N4 information includes an identifier of the UPF.

[0076] The first N4 information may be the same as the N4 information described in section 6.1.6.2.43 of 3GPP TS 29.502 V16.6.0, except that it further includes an identifier of the UPF.

[0077] In one embodiment, the first N4 information may be defined as shown in Table 4. In Table 4, an indicator "psaUpfId" is added to the first N4 information. [Table 4]

[0078] The first session management function may determine the first N4 information regarding the UPF in various ways. For example, the first session management function may receive the first N4 information regarding the UPF, which may include an identifier of the UPF. Alternatively, the first session management function may add an identifier of the UPF to the first N4 information regarding the UPF if the first N4 information regarding the UPF does not include an identifier of the UPF.

[0079] In a first embodiment, the first session management function can add an identifier of the UPF to the first N4 information. As a first example, the first session management function can receive a second message from the UPF, the second message including second N4 information related to the UPF. The second N4 information does not include an identifier of the UPF. In this case, the first session management function can add the identifier of the UPF to the second N4 information to generate the first N4 information.

[0080] In a second embodiment, the first session management function may receive a third message from the UPF, the third message including third N4 information related to the UPF. The third N4 information includes an identifier of the UPF. In this case, the first session management function may use the third N4 information as the first N4 information.

[0081] In a third embodiment, a first session management function may receive information about a UPF from a second session management function. The information about the UPF includes an identifier of the UPF. The first session management function may determine first N4 information about the UPF based on the information about the UPF. For example, the first session management function may add the identifier of the UPF to the first N4 information about the UPF.

[0082] At block 604, the first sending module may send a first message including the first N4 information to a second session management function. The second session management function may be an SMF or an I-SMF. For example, if the first session management function is an SMF, the second session management function may be an I-SMF. If the first session management function is an I-SMF, the second session management function may be an SMF.

[0083] The first message may be any suitable message that may be transmitted between the first session management function and the second session management function. For example, the first message may be a message containing N4 information transmitted between two SMFs as described in various 3GPP standards such as 3GPP TS 23.502 V16.7.0, 3GPP TS 29.502 V16.6.0, etc., except that the N4 information should be replaced with the first N4 information according to an embodiment of the present disclosure.

[0084] In one embodiment, the N4 information regarding UPF may be included in at least one of a session release message, a session update message, a session modification message, or a session report message. For example, the N4 information regarding UPF may be included in an Nsmf_PDUSession_Release Request, an Nsmf_PDUSession_Update Request, or an Nsmf_PDUSession_Update Response as described in 3GPP TS 23.502 V16.7.0, a PFCP Session Modification request / Response, a PFCP Session Deletion request / Response, or a PFCP Session Report request / Response as described in 3GPP TS 29.502 V16.6.0, At least one of may be included in

[0085] In one embodiment, the role of the N4 information may include at least one of the following: The N4 information is used by the session management function to report traffic usage for traffic offloaded by the UPF, or The N4 information is used by the session management function to control the traffic offloaded by the UPF.

[0086] In one embodiment, the UPF comprises a Protocol Data Unit Session Anchor (PSA) UPF.

[0087] 7 is a flowchart of a method according to another embodiment of the present disclosure. The method may be performed by an apparatus implemented in / as the first session management function, or an apparatus communicatively connected to the first session management function. Thus, the apparatus may provide means or modules for achieving various parts of the method 700, as well as means or modules for achieving other processes in cooperation with other components. Note that the description of parts already described in the previous embodiment will be omitted for brevity.

[0088] At block 702, the first session management function may receive a fourth message from the second session management function that includes fourth N4 information related to the UPF. The fourth N4 information includes an identifier of the UPF.

[0089] At block 704, the first session management function may send a fourth message to the UPF based on the identifier of the UPF.

[0090] For example, if the second session management function may need the first session management function to report traffic usage of the UPF offloaded traffic or to control the UPF offloaded traffic, the second session management function may send a fourth message to the first session management function, and the first session management function may then receive the fourth message.

[0091] 8 is a flowchart of a method according to another embodiment of the present disclosure. The method may be performed by an apparatus implemented in / as the second session management function, or an apparatus communicatively connected to the second session management function. Thus, the apparatus may provide means or modules for achieving various parts of the method 800, as well as means or modules for achieving other processes in cooperation with other components. Note that the description of parts already described in the previous embodiment will be omitted for brevity.

[0092] In block 802, the second session management function may receive a first message from the first session management function including first N4 information related to a user plane function (UPF). The first N4 information includes an identifier of the UPF. For example, the first session management function may send the first message to the second session management function in block 604 of FIG. 6, and the second session management function may then receive the first message.

[0093] In block 804, the second session management function may process the first message based on the identifier of the UPF. For example, depending on a particular type of the first message, the second session management function may perform corresponding processing. For example, if the first message is a message including N4 information as described in 3GPP TS 23.502 V16.7.0 and 3GPP TS 29.502 V16.6.0, the second session management function may perform corresponding processing as described in 3GPP TS 23.502 V16.7.0 and 3GPP TS 29.502 V16.6.0.

[0094] If necessary, in block 806, the second session management function may send a fourth message including the fourth N4 information regarding the UPF to the first session management function. The fourth N4 information includes an identifier of the UPF. For example, based on the processing result of block 804, the second session management function may send a fourth message including the fourth N4 information regarding the UPF to the first session management function. Alternatively, if the second session management function may need the first session management function to report traffic usage of the traffic offloaded at the UPF or to control the traffic offloaded at the UPF, the second session management function may send a corresponding fourth message to the first session management function.

[0095] In one embodiment, which PSA is N4 information N4 to indicate that information You can add the indicator "psaUpfId" to N4. information may be used by the I-SMF to report traffic usage reports to the SMF for traffic offloaded on a PSA controlled by the I-SMF, or may be used by the SMF to send N4 information to the I-SMF for control of traffic offloaded on a PSA controlled by the I-SMF.

[0096] In one embodiment, for the procedure as shown in FIG. 1, step 2 "I-SMF establishes PFCP session with PAS2" can be moved and integrated to step 7. If a new IPv6 prefix corresponding to PSA2 is assigned by UPF, step 2 cannot be moved and integrated to step 7. Then, in step 7, I-SMF interacts with PSA2 via N16a to provide the N4 rule determined in step 6. I-SMF also provides branching point or UL CL CN (Core Network) tunnel information for downlink traffic if PSA2 and UL CL / branching point are supported by different (one or more) UPFs. PSA2 CN tunnel information for local N9 termination on PSA2 can be determined. Then, in step 8, I-SMF updates the branching point or UL CL via N16a providing the N4 rule determined in step 6. I-SMF updates the branching point or UL CL with the PSA2 CN tunnel information. The advantage is that it saves the interaction between I-SMF and PSA2 and simplifies the processing of N4 information in N16a.

[0097] In one embodiment, step 2, "I-SMF establishes a PFCP session with PAS2" in the procedure shown in Figure 3 can be moved and consolidated into step 6. If a new IPv6 prefix corresponding to PSA2 is assigned by UPF, step 2 cannot be moved and consolidated into step 6. And steps 6 to 7 are the same as steps 7 to 8 in Figure 1. The advantage is that it saves the interaction between I-SMF and PSA2 and simplifies the processing of N4 information in N16a.

[0098] The embodiments of the present disclosure provide many advantages, some of which are listed below. In some embodiments of the present disclosure, the proposed solution allows the session management functions, such as the SMF and I-SMF, to identify which UPF (such as the PSA UPF) the N4 information corresponds to when multiple local UPFs (such as the PSA UPF) are inserted and controlled by the session management functions. In some embodiments of the present disclosure, the proposed solution can save the interaction between the session management functions, such as the I-SMF, and the UPFs, such as the PSA UPF. In some embodiments of the present disclosure, the proposed solution can simplify the handling of the N16a N4 information. The embodiments of the present disclosure are not limited to the above-mentioned features and advantages. The skilled person will recognize additional features and advantages from reading the following detailed description.

[0099] The various blocks illustrated in Figures 6-8 may be considered as steps of a method and / or as operations resulting from the operation of computer program code and / or as multiple combined logic circuit elements configured to perform the associated functions. The schematic flow charts described above are generally described as logical flow charts. As such, the illustrated order and labeled steps are indicative of particular embodiments of the presented method. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more steps, or portions thereof, of the illustrated method. Additionally, the order of execution of a particular method may or may not strictly follow the order of the corresponding steps illustrated.

[0100] 9 is a block diagram showing an apparatus suitable for implementing some embodiments of the present disclosure. For example, any one of the first and second session management functions described above may be implemented as or through an apparatus 900.

[0101] The apparatus 900 comprises at least one processor 921, such as a digital processor (DP), and at least one memory (MEM) 922 connected to the processor 921. The apparatus 920 may further comprise a transmitter TX and a receiver RX 923 connected to the processor 921. The MEM 922 stores a program (PROG) 924. The PROG 924 may include instructions that, when executed on an associated processor 921, enable the apparatus 920 to operate according to embodiments of the present disclosure. The combination of the at least one processor 921 and the at least one MEM 922 may form a processing means 925 adapted to perform various embodiments of the present disclosure.

[0102] Various embodiments of the present disclosure may be implemented by computer programs executable by one or more of the processor(s) 921, software, firmware, hardware, or combinations thereof.

[0103] MEM922 may be of any type suitable for the local technology environment and may be implemented using any suitable data storage technology, such as, but not limited to, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.

[0104] The processor 921 may be of any type suitable for the local technology environment and may include, by way of non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture.

[0105] In one embodiment in which the apparatus is implemented as or with a first session management function, memory 922 stores instructions executable by processor 921 such that the first session management function functions according to any of the methods relating to the first session management function described above.

[0106] In one embodiment in which the apparatus is implemented as or with a second session management function, memory 922 stores instructions executable by processor 921 such that the second session management function operates according to any of the methods for the second session management function described above.

[0107] 10 is a block diagram illustrating a first session management function according to an embodiment of the present disclosure. As shown, the first session management function 1000 includes a determining module 1001 and a first sending module 1002. The determining module 1001 may be configured to determine first N4 information related to a user plane function (UPF). The first N4 information includes an identifier of the UPF. The first sending module 1002 may be configured to send a first message including the first N4 information to a second session management function.

[0108] In one embodiment, the first session management function 1000 may further include a receiving module 1003 configured to receive a fourth message from the second session management function, the fourth message including fourth N4 information related to the UPF. The fourth N4 information includes an identifier of the UPF.

[0109] In one embodiment, the first session management function 1000 may further include a second sending module 1004 configured to send a fourth message to the UPF based on the identifier of the UPF.

[0110] 11 is a block diagram illustrating a second session management function according to an embodiment of the present disclosure. As shown, the second session management function 1100 includes a receiving module 1101 and a processing module 1102. The receiving module 1101 may be configured to receive a first message including first N4 information related to a user plane function (UPF) from a first session management function. The first N4 information includes an identifier of the UPF. The processing module 1102 may be configured to process the first message based on the identifier of the UPF.

[0111] In one embodiment, the second session management function 1100 may further include a sending module 1103 configured to send a fourth message including fourth N4 information related to the UPF to the first session management function, the fourth N4 information including an identifier of the UPF.

[0112] The terms "unit" or "module" may have their conventional meaning in the electronics, electric equipment, and / or electronics fields and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logic semiconductor and / or discrete devices, computer programs or instructions, etc., for performing a respective task, procedure, computation, output, and / or display function, such as those described in this disclosure.

[0113] By having the functional units, the above-mentioned first session management function and second session management function do not require fixed processors or memories, and any computing resources and storage resources can be allocated from the first session management function and the second session management function in the communication system. The introduction of virtualization technology and network computing technology can improve the utilization efficiency of network resources and the flexibility of the network.

[0114] According to one aspect of the present disclosure, there is provided a computer program product comprising instructions tangibly stored on a computer-readable storage medium and which, when executed on at least one processor, cause the at least one processor to perform any of the methods described above.

[0115] According to one aspect of the present disclosure, there is provided a computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform any of the methods set forth above.

[0116] The present disclosure may further provide a carrier comprising the above-mentioned computer program, the carrier being one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium, which may be, for example, a RAM (random access memory), a ROM (read only memory), a flash memory, a magnetic tape, an optical compact disc, such as a CD-ROM, a DVD, a Blu-ray disc, or an electronic memory device.

[0117] The techniques described in this disclosure may be implemented by various means, such that an apparatus performing one or more functions of a corresponding apparatus described in connection with an embodiment may have means for performing one or more of those functions in addition to means according to the prior art, and such an apparatus may have separate means for each individual function, or means that may be configured to perform two or more functions. For example, these techniques may be implemented in hardware (one or more units), firmware (one or more units), software (one or more modules), or a combination thereof. In the case of firmware or software, the implementation may be through modules (e.g., procedures, functions, etc.) that perform the functions described in this disclosure.

[0118] Exemplary embodiments of the present disclosure have been described with reference to block diagrams and flow charts of methods and apparatus. It will be understood that each block of the block diagrams and flow charts, and combinations of blocks in the block diagrams and flow charts, respectively, can be implemented by various means including computer program instructions. These computer program instructions may be loaded into a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine such that the instructions, which execute on a computer or other programmable data processing apparatus, create means for implementing the functions described in one or more blocks of the flow charts.

[0119] Furthermore, although operations are illustrated in a particular order, this should not be construed as requiring such operations to be performed in the particular order illustrated, or in sequential order, or to perform all of the illustrated operations, in order to achieve desirable results. In some circumstances, multitasking or parallel processing may be advantageous. Similarly, although details of some specific implementations are included in the above discussion, these should not be construed as limitations on the scope of the subject matter described in this disclosure, but rather as illustrations of features that may be unique to particular implementations. Some features that are described in the context of separate embodiments may be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may be implemented in multiple embodiments separately or in any suitable combination.

[0120] Although many specific implementation details are described herein, these should not be construed as limitations on the scope of any implementation or what may be claimed, but rather as descriptions of features that may be specific to a particular embodiment of a particular implementation. Some features described in the context of separate embodiments herein may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable combination. Furthermore, although features may be described as acting in a particular combination, and even initially claimed as such, one or more features from a claimed combination may in some cases be excluded from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination.

[0121] It will be obvious to those skilled in the art that with the advancement of technology, the concept of the present invention can be implemented in various ways. The above-mentioned embodiments are given to illustrate, not to limit, the present disclosure, and it should be understood that modifications and variations can be adopted without departing from the spirit and scope of the present disclosure, as easily understood by those skilled in the art. Such modifications and variations are deemed to be included in the scope of the present disclosure and the appended claims. The scope of protection of the present disclosure is defined by the appended claims.

Claims

1. A method (600) performed by a first session management function, comprising: determining (602) first N4 information for a User Plane Function (UPF), where the UPF supports a Protocol Data Unit (PDU) session having a plurality of PDU Session Anchors (PSAs), the first N4 information including an identifier of one of the plurality of PSAs of the UPF to which the first N4 information applies; Sending (604) a first message including the first N4 information to a second session management function; The method comprising:

2. Determining the first N4 information regarding the UPF includes: receiving a second message from the UPF including second N4 information related to the UPF, where the second N4 information does not include the identifier of the one of the plurality of PSAs of the UPF; appending the identifier of the one of the plurality of PSAs of the UPF to the second N4 information to generate the first N4 information; 2. The method of claim 1, having the following structure:

3. Determining the first N4 information regarding the UPF includes: receiving a third message from the UPF including third N4 information related to the UPF, where the third N4 information includes the identifier of the one of the plurality of PSAs of the UPF; using the third N4 information as the first N4 information; 2. The method of claim 1, having the following structure:

4. receiving (702) a fourth message from the second session management function including fourth N4 information related to the UPF, where the fourth N4 information includes the identifier of the one of the plurality of PSAs of the UPF; sending (704) the fourth message to the one of the plurality of PSAs of the UPF based on the identifier of the one of the plurality of PSAs of the UPF; 4. The method of claim 1, further comprising:

5. The method of claim 1 , wherein the first session management function comprises an intermediate session management function.

6. The N4 information regarding the UPF, Session release message, Session update messages, a session modification message, or Session Report Message The method according to any one of claims 1 to 5, wherein the method is included in at least one of the following:

7. The role of the N4 information is The N4 information is used by a session management function to report traffic usage of offloaded traffic at the UPF; or The N4 information is used by a session management function to control traffic offloaded by the UPF; The method according to any one of claims 1 to 6, comprising at least one of the following:

8. A method (800) performed by a second session management function, comprising: receiving 802 a first message from a first session management function including first N4 information related to a user plane function (UPF), where the UPF supports a PDU session having a plurality of Protocol Data Unit (PDU) Session Anchors (PSAs), the first N4 information including an identifier of one of the plurality of PSAs of the UPF to which the first N4 information applies; processing (804) the first message based on the identifier of the one of the plurality of PSAs of the UPF; The method comprising:

9. 9. The method of claim 8, further comprising: sending (806) a fourth message to the first session management function including fourth N4 information regarding the UPF, the fourth N4 information including the identifier of the one of the plurality of PSAs of the UPF.

10. 10. The method of claim 8 or 9, wherein the first session management function comprises at least one intermediate session management function.

11. The N4 information regarding the UPF, Session release message, Session update messages, a session modification message, or Session Report Message The method according to any one of claims 8 to 10, wherein the method is included in at least one of the following:

12. The role of the N4 information is The N4 information is used by a session management function to report traffic usage of offloaded traffic at the UPF; or The N4 information is used by a session management function to control traffic offloaded by the UPF; The method according to any one of claims 8 to 11, comprising at least one of the following:

13. A first session management function (900), A processor (921); a memory (922) connected to said processor (921), said memory (922) storing instructions executable by said processor (921), whereby said first session management function (900) Determine first N4 information for a User Plane Function (UPF), where the UPF supports a PDU session having a plurality of Protocol Data Unit (PDU) Session Anchors (PSAs), and the first N4 information includes an identifier of one of the plurality of PSAs of the UPF to which the first N4 information applies; sending a first message including the first N4 information to a second session management function; A first session management function operable to:

14. A first session management function according to claim 13, wherein the first session management function is further operable to perform a method according to any one of claims 2 to 7.

15. A second session management function (900), A processor (921); and a memory (922) connected to the processor (921), the memory (922) storing instructions executable by the processor (921), whereby the second session management function (900) receiving a first message from a first session management function including first N4 information related to a user plane function (UPF), where the UPF supports a PDU session having a plurality of Protocol Data Unit (PDU) Session Anchors (PSAs), the first N4 information including an identifier of one of the plurality of PSAs of the UPF to which the first N4 information applies; processing the first message based on the identifier of the one of the plurality of PSAs of the UPF. A second session management function operable to:

16. A second session management function according to claim 15, wherein the second session management function is further operable to perform a method according to any one of claims 9 to 12.

17. A computer program comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 7.

18. A computer program comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 8 to 12.

Images