Method and apparatus for optimizing session establishment across devices

Abstract

A method performed by a network entity configured for connection and management services is provided. The method includes receiving, from a user equipment, a service descriptor that has been started by the user equipment for use; determining a set of data session attributes for a service described by the service descriptor based on information about capabilities of the user equipment and information obtained from an entity of a communication network; and providing the set of data session attributes to a second core network entity or the user equipment, the set of data session attributes to be used by the second core network entity or the user equipment for establishing a data session for the service or modifying an existing data session for the service.

Description

Technical Field

[0001] This disclosure generally relates to communication networks. More specifically, this disclosure relates to a communication network that initiates the establishment or modification of a data session with a data network, or triggers (e.g., instructs) a user equipment to request the establishment or modification of a data session with a data network. Background Technology

[0002] Mobile telecommunications networks or cellular networks (often referred to as communication networks in this document) enable communication between two or more communication devices (also known as user equipment), provide communication devices with access to data networks, deliver services provided by third-party applications to communication devices, or provide communication devices with services provided by the communication network.

[0003] Communication networks and equipment can operate based on cellular technologies (also known as radio access technologies), such as GSM, UTMS, LTE, LTE-A, and NR. Cellular technologies are standardized by various standards organizations, such as the 3rd Generation Partnership Project (3GPP) or ETSI (European Telecommunications Standards Institute). 3GPP is currently developing fifth-generation cellular technology standards (commonly referred to as 5G or NR standards) and sixth-generation cellular technology standards (commonly referred to as 6G standards). Communication networks operating according to 5G or NR standards are generally called 5G networks, while communication networks operating according to 6G standards are generally called 6G networks.

[0004] Communication networks (e.g., 5G or 6G networks) include access networks (e.g., radio access networks) that can wirelessly communicate with one or more communication devices by sharing the available resources (e.g., bandwidth, transmit power, etc.) of the access network. Communication networks can also establish reliable and secure connections between communication devices and data networks. Communication networks (e.g., 5G networks) can provide communication devices with enhanced mobile broadband services (e.g., telephony, video, data, short message service, messaging service), ultra-reliable low-latency communication services, or massive machine-type communication services. Summary of the Invention

[0005] Various aspects of exemplary implementations of this disclosure are set forth in the independent and dependent claims.

[0006] This disclosure relates to a communication network (not a user equipment) that initiates or modifies a data session with a data network via a communication network.

[0007] According to a first aspect of this disclosure, a first network entity of a communication network is provided, the first network entity being configured to perform operations including: receiving from a user equipment a service descriptor that has been initiated for use by the user equipment; determining a set of data session attributes for the service described by the service descriptor based on information about the capabilities of the user equipment and information obtained from an entity of the communication network; and providing the set of data session attributes to a second core network entity or the user equipment, the set of data session attributes being used by the second core network entity or the user equipment to establish a data session for the service or to modify an existing data session for the service.

[0008] According to a second aspect, an apparatus for a communication network is provided, the apparatus comprising: a first network entity configured to perform operations including: receiving from a user equipment a service descriptor that has been initiated for use by the user equipment; determining a set of data session attributes for a service described by the service descriptor based on information about the capabilities of the user equipment and information obtained from an entity of the communication network; and providing the set of data session attributes to a second core network entity or the user equipment for establishing a data session for the service or modifying an existing data session for the service.

[0009] According to a third aspect of this disclosure, a method for managing network functions of connections and services in a communication network is provided. The method includes: receiving from a user equipment (UE) a service descriptor that has begun to be used by the UE; determining a set of data session attributes for the service described by the service descriptor based on information about the UE's capabilities and information obtained from entities within the communication network; and providing the set of data session attributes to a second core network entity or the UE, the set of data session attributes being used by the second core network entity or the UE to establish a data session for the service or to modify an existing data session for the service.

[0010] According to a fourth aspect of this disclosure, a computer program including instructions for a first core network entity is provided, wherein when the computer program is executed by at least one processor of an apparatus, the apparatus is caused to perform operations including: receiving from a user equipment a service descriptor that has been initiated for use by the user equipment; determining a set of data session attributes for the service described by the service descriptor based on information about the capabilities of the user equipment and information obtained from an entity of the communication network; and providing the set of data session attributes to a second core network entity or the user equipment, the set of data session attributes being used by the second core network entity or the user equipment to establish a data session for the service or to modify an existing data session for the service.

[0011] According to a fifth aspect of this disclosure, a computer-readable medium (e.g., a non-transitory computer-readable medium including instructions) is provided for a first core network entity, wherein the instructions, when executed by at least one processor of the apparatus, cause the apparatus to perform operations including: receiving from a user equipment a service descriptor that has been initiated for use by the user equipment; determining a set of data session attributes for the service described by the service descriptor based on information about the capabilities of the user equipment and information obtained from an entity of the communication network; and providing the set of data session attributes to a second core network entity or the user equipment, the set of data session attributes being used by the second core network entity or the user equipment to establish a data session for the service or to modify an existing data session for the service.

[0012] According to a sixth aspect of this disclosure, a user equipment is provided, the user equipment including at least one processor; and at least one memory storing instructions, which, when executed by the at least one processor, cause the user equipment to perform operations including: sending a service descriptor that has begun to be used by the user equipment to a first core network entity of a communication network; receiving a data session attribute set from the first core network entity, the data session attribute set being used to establish a new data session for a service described by the service descriptor or to modify an existing data session for a service described by the service descriptor; and initiating the establishment of a new data session or the modification of an existing data session based on the data session attribute set.

[0013] According to a seventh aspect of this disclosure, a method for a user equipment is provided. The method includes: sending a service descriptor that has begun to be used by the user equipment to a first core network entity of a communication network; receiving a data session attribute set from the first core network entity, the data session attribute set being used to establish a new data session for the service described by the service descriptor or to modify an existing data session for the service described by the service descriptor; and initiating the establishment of a new data session or the modification of an existing data session based on the data session attribute set.

[0014] According to an eighth aspect of this disclosure, a computer program including instructions is provided, wherein when the computer program is executed by at least one processor of a user equipment, the user equipment is caused to perform operations including: sending a service descriptor that has begun to be used by the user equipment to a first core network entity of a communication network; receiving a data session attribute set from the first core network entity, the data session attribute set being used to establish a new data session for the service described by the service descriptor or to modify an existing data session for the service described by the service descriptor; and initiating the establishment of a new data session or the modification of an existing data session based on the data session attribute set.

[0015] According to a ninth aspect of this disclosure, a computer-readable medium (e.g., a non-transitory computer-readable medium) is provided that includes instructions, which, when executed by at least one processor of a user equipment, cause the user equipment to perform operations including: sending a service descriptor that has begun to be used by the user equipment to a first core network entity of a communication network; receiving a data session attribute set from the first core network entity, the data session attribute set being used to establish a new data session for the service described by the service descriptor or to modify an existing data session for the service described by the service descriptor; and initiating the establishment of a new data session or the modification of an existing data session based on the data session attribute set.

[0016] The foregoing description provides a basic understanding of some aspects of this disclosure. This description is not a broad summary of the disclosure, nor is it intended to limit its scope. Other aspects and features of this disclosure will become apparent to those skilled in the art upon reading the following description of exemplary implementations in conjunction with the accompanying drawings. Attached Figure Description

[0017] The accompanying drawings, which illustrate an example implementation of this application, will now be referenced by way of example. In the drawings:

[0018] Figure 1 This is a schematic block diagram illustrating user equipment, communication networks, and data networks implemented according to an example;

[0019] Figure 2 The diagram is based on the example. Figure 1 A schematic diagram of the physical and logical components of a communication network device;

[0020] Figure 3 This is a schematic diagram illustrating the physical and logical components of a communication device implemented according to an example;

[0021] Figure 4 This is a schematic diagram of the physical and logical components of the core network of a communication network implemented according to an example;

[0022] Figure 5 This is a schematic diagram of the physical and logical components of the core network of a communication network implemented according to another example;

[0023] Figure 6 This is a schematic diagram of the physical and logical components of the core network of a communication network implemented according to another example;

[0024] Figure 7 This is a flowchart illustrating a method for initiating and establishing a data session in a communication network, implemented according to an example.

[0025] Figure 8This is a flowchart illustrating a method for initiating a modification of an existing data session in a communication network, implemented according to an example.

[0026] Figure 9 This is a flowchart illustrating a method for initiating the release of an existing data session in a communication network, implemented according to an example.

[0027] Figure 10 This is a flowchart illustrating a method executed by a network entity in a communication network, implemented according to an example; and

[0028] Figure 11 This is a flowchart illustrating a method executed by a user device, implemented according to an example.

[0029] Similar reference numerals have been used in different drawings to denote similar components. Unless otherwise specified, the items depicted in the drawings are not necessarily drawn to scale. Detailed Implementation

[0030] The subject matter is described herein with reference to the accompanying drawings, which illustrate example implementations. However, many different example implementations may be used, and therefore this description should not be construed as limiting it to the embodiments described herein. Rather, these example implementations are provided to make the application thorough and complete. Where possible, the same reference numerals are used in the drawings and the following description to refer to the same elements, and prime numbers are used to indicate similar elements, operations, or steps in alternative example implementations. The separate blocks or separations of logical elements in the illustrated systems and devices do not necessarily require physical separation of such logical elements, as communication between such logical elements can occur through message passing, function calls, shared memory spaces, etc., without any such physical separation. Therefore, logical elements do not need to be implemented in physically or logically separate platforms, although such logical elements are shown separately for ease of explanation. Different devices may have different designs such that while some devices implement some logical elements in hardware, others may implement such logical elements in a programmable processor with code obtained from machine-readable media. Finally, the element referred to by the singular may be plural, and vice versa, unless the context explicitly or inherently indicates otherwise.

[0031] References to “an implementation,” “implementation,” “example implementation,” etc., in this disclosure indicate that the described implementation may include a particular feature, structure, or characteristic, but not every implementation must include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same implementation. Moreover, when a particular feature, structure, or characteristic is described in conjunction with an implementation, it is understood that a person skilled in the art could implement that feature, structure, or characteristic in conjunction with other implementations, whether explicitly described or not.

[0032] For the purposes of this disclosure, the phrases "at least one of A or B", "at least one of A and B", and "A and / or B" refer to (A), (B), or (A and B). For the purposes of this disclosure, the phrases "A, B, and / or C" refer to (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0033] User equipment located within an area served by a communication network (e.g., within the service area of ​​the communication network) can register with the communication network. After registering with the communication network, the user equipment can request to establish a data connection (also known as a data session) with a data network through the communication network, for example, to provide the user equipment with access to the data network and / or to receive services provided by third-party application providers via the data network and the communication network.

[0034] For example, in a communication network operating according to LTE, a user equipment (also called a communication device) can be attached to the communication network, and after being attached, it can request to establish a packet data network (PDN) connection with the data network through the PDN gateway of the communication network by sending a PDN connection request to the communication network. Upon receiving the PDN connection request, the communication network can establish a PDN connection for the user equipment, as per 3GPP TS 23.401. Figure 5 As shown in .10.2-1.

[0035] For communication networks operating according to NR, user equipment (UE) can register with the communication network. After registration, the UE can request to establish a Protocol Data Unit (PDU) session with the data network via the UE's User Plane Function (UFP) by sending a PDU Session Establishment Request to the communication network. The communication network (e.g., the core network of the communication network) establishes the PDU session, as per 3GPP TS 23.502. Figure 4 As shown in 3.2.2-1.

[0036] A PDN connection request may include one or more attributes of a PDN connection that the user equipment is requesting to establish on the communication network. Similarly, a PDU session establishment request may include one or more attributes of a PDU session that the communication equipment is requesting to establish on the communication network. Examples of PDU session attributes include the type of PDU session to be established (e.g., Internet Protocol version 4 (IPv4) session, IP version 6 (IPv6) session, and IP version 4 and version 5 (IPv4v6) sessions, or an Ethernet session), the session and service continuity mode used for the PDU session (e.g., SCC mode 1, SCC2 mode 2, or SSC mode 3), the identifier of the network slice through which the PDU session is to be established, and the data network name (DNN) of the data network with which the PDU session is to be established.

[0037] The User Equipment (UE) determines the set of attributes for the PDN connection to be included in the PDN connection request or the set of attributes for the PDU session to be included in the PDU session establishment request based on information received from various sources. For example, the UE may receive information from policy control functions of the communication network, access and mobility functions of the communication network, session management functions of the communication network, and radio access network nodes of the communication network. The UE determines the set of attributes for the PDU session based on the information received by the UE.

[0038] For example, a UE can receive a User Equipment Selection Policy (URSP) from the policy control function of the communication network and determine the attribute set of a PDU session based on the URSP received from the PCF. An URSP includes one or more URSP rules, and each corresponding URSP in the one or more URSP rules indicates the attribute set that the UE should use for a PDN connection or PDU session for a given application. Each URSP rule includes a Service Descriptor (TD) indicating the application, and a Routing Descriptor (RSD) includes the attribute set of the PDU session that the UE wants to request to establish.

[0039] Alternatively, the application layer in the UE can request a connection to another layer in the UE, such as the URSP processing layer in the UE. The application layer provides...

[0040] During the UE's registration with the communication network, the UE can receive network slice information from the communication network's Access and Mobility Function (AMF). The network slice information includes Single Network Slice Auxiliary Information (S-NSSAI) to be permitted by the communication network for each network slice used by the UE.

[0041] The limitations of the PDU establishment process described above are as follows. PDU session establishment requests or PDU session modification requests sent by the UE to the communication network may be rejected by the communication network (e.g., the SMF of the communication network), not only due to congestion in the communication network, but also for other reasons. For example, PDU session establishment requests or PDU session modification requests sent by the UE to the communication network may be rejected by the communication network (e.g., the SMF of the communication network) due to a lost or unknown Data Network Name (DNN) and / or S-NSSAI, an unknown or disallowed PDU session type, or an unsupported SSC mode. Furthermore, UE behavior has become inconsistent after receiving a rejection message from the communication network. For example, according to the Global System for Mobile Communications Association (GSMA), some UEs send another request shortly after receiving a rejection message, while some UEs never send a request after receiving a rejection message.

[0042] This disclosure describes a communication network including core network functions configured to determine a set of attributes for a data session when a core network entity or core network function receives an indication from a communication device that a service descriptor has been initiated. The communication network includes a core network entity that enables another core network function or communication device within the communication network to initiate or modify a data session with a data network, or triggers (e.g., instructs) a communication device to request the establishment or modification of a data session with a data network via the communication network. The core network function may be a core network function configured to perform data connection and service management (referred to herein as the Connection and Service Management Function (CSAF)) of the communication network. The primary function of the CSAF is to determine data session attributes. The CSAF may be configured to receive information from a user equipment (UE) regarding the UE's capabilities (typically referred to as UE capabilities). For example, the UE may provide information about its capabilities to the CSAF by sending a control plane message that includes information about its capabilities. Alternatively, the UE can provide its capabilities to a core network function of the communication network, which stores the UE's capabilities. The CSAF can obtain the UE's capabilities from the core network function by sending a request for the UE's capabilities to the core network function that stores the UE's capabilities. Examples of information regarding the UE's capabilities include information indicating the maximum number of data sessions supported by the UE, information indicating the data session attributes supported by the UE, and other information regarding the UE's capabilities. This other information regarding the UE's capabilities can be indicated to the CSAF via 5GSM capability information elements. This other information includes one or more of the following: information indicating that the UE supports Reflective Quality of Service (RQoS); information indicating that the UE supports multi-homed IPv6 PDU sessions; information indicating that the UE supports Access Service Bootstrapping, Handover and Split (ATSSS) bootstrapping functions and bootstrapping modes; information indicating that the UE supports the transmission of port management information containers; information indicating that the UE supports access performance measurements according to QoS flow rules (e.g., for corresponding QoS flow rules); or information indicating that the UE supports secondary data network authentication and authorization on the Evolved Packet Core (EPC).

[0043] CSAF is also configured to obtain information about the communication network from radio access network nodes of the radio access network (RAN) of the communication network that serve user equipment registered with the communication network and from various core network functions of the communication network.

[0044] For example, the CSAF can be configured to obtain information about RAN nodes serving the user equipment from the radio access network nodes serving the user equipment. This information may include RAN resource status information and / or information about network slices supported by the RAN nodes serving the user equipment. The RAN resource status information indicates the resource status of the RAN nodes serving the user equipment. The RAN nodes can directly provide the CSAF with the RAN resource status information and / or information indicating network slices supported by the RAN nodes by sending control plane signaling (e.g., control plane messages), which includes the RAN resource status information and / or information about network slices supported by the RAN nodes serving the user equipment. Alternatively, the RAN nodes can provide the AMF with the RAN resource status information and / or information indicating network slices supported by the RAN nodes by sending control plane signaling (e.g., control plane messages) to the access and mobility (AMF) of the communication network. Upon receiving control plane signaling (e.g., control plane messages), the AMF can provide the CSAF with RAN resource status and / or information indicating network slices supported by RAN nodes by, for example, sending control plane signaling including RAN resource status information and / or information indicating network slices supported by RAN nodes.

[0045] The CSAF can also be configured to obtain user equipment location information from the Access and Mobility Function (AMF) of the communication network. The user equipment location information indicates the location of the user equipment. The user equipment location information may include a cell identifier identifying the cell in which the user equipment resides, or a tracking area identifier identifying the tracking area in which the user equipment resides. The CSAF can obtain the user equipment location information from the AMF by requesting the AMF to provide the user equipment location information to the CSAF (e.g., by sending a request for user equipment location information to the AMF). The AMF can respond to a request for user equipment location information sent by the CSAF by sending a response to the CSAF including the user equipment location information. Alternatively, the CSAF can obtain the user equipment location information from the AMF by sending a subscription request for user equipment location information to the AMF. Upon receiving the subscription request, the AMF generates a subscription that periodically or whenever the UE's location changes, notifying the CSAF of the user equipment location information. The AMF notifies the CSAF of the user equipment location information by sending a notification to the CSAF including the user equipment location information (e.g., cell identifier, tracking area identifier, identifier of a set of tracking areas). Alternatively, after the AMF receives a message from the UE that should be forwarded to the CSAF, the AMF sends the user equipment location information along with the message to the CSAF.

[0046] The CSAF can also be configured to obtain subscription information associated with the user equipment (UE) subscriber from the Unified Data Management (UDM) entity of the communication network, as well as information instructing the UE to register with the communication network via one or more access types (referred to herein as UE access type information). The UE access type information may include information instructing the UE to register with the communication network via 3GPP access only, via non-3GPP access only, or via both 3GPP and non-3GPP access. The term "3GPP access" refers to an access network operating according to 3GPP standards, and the term "non-3GPP access" refers to an access network not operating according to 3GPP standards (e.g., WiFi™ access points, wired access points, etc.). The CSAF can obtain the subscription information associated with the UE subscriber and the UE access type information from the UDM entity by requesting the UDM entity to provide the subscription information associated with the UE subscriber (e.g., by sending a request to the UDM for the subscription information associated with the UE subscriber and the UE access type information). UDM can respond to a request sent by CSAF by sending a response to the request to CSAF, which includes subscription information and user equipment access type information associated with the user equipment subscriber.

[0047] The CASF can also be configured to obtain user equipment policy information (referred to herein as user equipment policy information) from the policy control function (PCF) of the communication network. This user equipment policy information includes a mapping from service descriptors to data session attribute sets. The user equipment policy information can be included in the user equipment routing policy (URSP) provided by the PCF to the CSAF. The CSAF can obtain the user equipment policy information by requesting it from the PCF (e.g., by sending a request for user equipment policy information to the PCF). The PCF can respond to the request sent by the CSAF by sending a response to the request that includes the user equipment policy information.

[0048] CSAF can also be configured to obtain information about network slice restrictions of the communication network from the Network Slice Selection Function (NSSF) of the communication network. The network slice restriction information of the communication network (referred to herein as network slice restriction information) includes the time when network slices are available in the communication network, the location where network slices are available, and the maximum number of data sessions allowed for each corresponding network slice of the communication network.

[0049] CSAF can also be configured to obtain network slice replacement information from the Network Slice Admission Control Function (NSACF) of the communication network. Network slice replacement information is information indicating the identifier of a network slice subscribed to by a user equipment, which can replace another network slice in the communication network.

[0050] The CSAF can also be configured to obtain information from the Network Repository Function (NRF) of the communication network to assist in the selection of the Session Management Function (SMF) of the communication network (referred to herein as SMF selection assistance information). SMF selection assistance information is used by the CSAF to select an SMF that can initiate the establishment of a data session for a user equipment. SMF selection assistance information includes, for example, SMF resource status information and information indicating which network slices of the communication network the SMF supports. SMF resource status information is information indicating the resource status of the SMF, such as the SMF's load status expressed as a percentage. Information indicating which network slices of the communication network the SMF supports includes identifiers of the network slices supported by the SMF.

[0051] Now for reference Figure 1 The example illustrates a communication network 100 configured to initiate the establishment of a new data session from user equipment 102 to data network 104 via communication network 100, or to modify an existing data session from user equipment 102 to data network 104 via communication network 100. Figure 1 The illustrated communication network 100 includes a radio access network (RAN) 106 and a core network 108 (e.g., a 5G core network (5GC)). RAN 106 may be a RAN operating according to a fifth-generation radio access technology (RAT), such as the RAT described in the 3rd Generation Partnership Project (3GPP) standard for New Radio (NR), commonly referred to as a Next Generation Radio Access Network (NG-RAN). Core network 108 may also operate according to a fifth-generation RAT described in the 3GPP standard for NR. Core network 108 includes network functions (commonly referred to as network function 110, collectively referred to as network function 110). Core network 108 has a service-based architecture as described in further detail below.

[0052] although Figure 1 The communication network 100 shown includes RAN 106, but in some implementations, the communication network 100 may also include an access network (not shown) configured to connect user equipment (e.g., communication equipment 102) to core network 108 via an interworking function (not shown).

[0053] RAN 106 includes one or more Radio Access Network (RAN) nodes (also called base stations). RAN nodes can provide one or more cells. For example, a cell can be a macro cell, micro cell, femtocell, or picocell. A cell defines the coverage area or service area of ​​a RAN node. RAN nodes can be, for example, Node Bs (NodeBs or NBs), evolved Node Bs (eNodeBs or eNBs), next-generation Node Bs (gNBs), Remote Radio Units (RRUs), Remote Radio Headers (RRHs), relays, Integrated Access and Backhaul (IAB) nodes, and low-power nodes. RAN nodes can be deployed in non-terrestrial network (NTN) equipment, such as satellites (e.g., low Earth orbit (LEO) or geostationary orbit (GEO) satellites), aircraft, or drones, where such NTN equipment forms a non-terrestrial network, such as a ground station. RAN nodes can also be deployed on groups, in which case the RAN nodes can be referred to as terrestrial network equipment. RANs that include terrestrial network equipment are generally referred to as terrestrial networks.

[0054] RAN nodes can have a split architecture, where the functionality of the RAN node (e.g., eNB or gNB) is distributed among various entities. A RAN node with a split architecture can include Radio Units (RUs) (also known as Remote Radio Headers (RRHs)), Centralized Units (CUs), and one or more Distributed Units (DUs). DUs can be connected to RUs via fronthaul. DUs can be connected to CUs via midhaul or F1 interfaces. CUs can be connected to the core network (e.g., Core Network 108) via backhaul. In a RAN node with a split architecture, the operation of the RAN node can be performed by CUs and DUs. One CU can control one or more DUs.

[0055] The RU converts radio signals sent to and from the antenna into digital signals for transmission over a packet network, handles the digital front-end (DFE) and lower PHY layers, and includes digital beamforming capabilities. A DU is a logical entity (e.g., software) hosted on and running on a server near the RU. A CU is a logical entity (e.g., software) hosted on and running on a server. A CU can be hosted on its own server and run on that server, or it can be hosted on the same server hosting and running the DU. A DU includes a subset of the RAN node's functionality (e.g., eNB or gNB) depending on the functional breakdown, and a CU includes additional RAN node functionality not included in the DU's functional subset. A DU can include a subset of the layers of the RAN node's protocol stack, and a CU can include additional layers of the protocol stack not included in the DU's subset of layers. For example, in some implementations, the DU may include the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and Physical (PHY) layer of the protocol stack for the RAN node, while the CU may include layers of the RAN node's protocol stack above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, Radio Resource Control (RRC) layer, and Internet Protocol (IP) layer. The operation of the DU is controlled by the CU.

[0056] Now for reference Figure 2 It shows Figure 1 The communication network 100 has a core network 108 with a service-based architecture. The network functions 110 of the core network 108 (also referred to as core network functions 110) include Access and Mobility Function (AMF), Authentication Server Function (AUSF), Network Exposure Function (NEF), Network Repository Function (NRF), Network Slice Selection Function (NSSF), Policy Control Function (PCF), Session Management Function (SMF), User Plane Function (UPF), Union Data Repository (UDM), and network functions configured to perform connection and service management of the communication network 100, referred to herein as Connection and Service Management Function (CSAF) as described above. For ease of illustration, Figure 1 Other network functions 110 of the core network 108, such as Binding Support Function (BSF) and Billing Function (CHF), are not shown in the diagram.

[0057] The network functions 110 of core network 108 are interconnected via service-based interfaces (SBIs). AMF has a service-based interface (SBI), Namf, which is used by other network functions 110 of core network 108 to communicate with AMF. AUSF has an SBI, Nausf, which is used by other network functions 110 of core network 108 to communicate with AUSF. NEF has an SBI, Nnef, which is used by other network functions 110 of core network 108 to communicate with NEF. NRF has an SBI, Nnrf, which is used by other network functions 110 of core network 108 to communicate with NRF. NSSF has an SBI, Nnssf, which is used by other network functions 110 of core network 108 to communicate with NSSF. The PCF has an SBI and an Npcf, which are used by other network functions 110 of the core network 108 to communicate with the PCF; the SMF has an SBI and an Nsmf, which are used by other network functions 110 of the core network 108 to communicate with the SMF; the UDM has an SBI and an Nudm, which are used by other network functions 110 of the core network 108 to communicate with the UDM; and the CSAF has an SBI and an Ncsaf, which are used by other network functions 110 to communicate with the CSAF.

[0058] The AMF also has control plane interfaces N2 and N3. Communication device 102 can communicate with the AMF via N2, and RAN nodes of RAN 106 can communicate with the AMF via N3. The UPF has a data plane interface through which the RAN transmits data between communication device 102 and the UPF. The UPF includes interfaces configured for communication with other UPFs in the core network. Furthermore, the UPF has interface N6 through which it communicates with the data network 104.

[0059] AMF processes access, authorization, and authentication of user equipment (including UE 100), and manages the mobility of user equipment 100 when it moves between different radio access networks, cells, or locations.

[0060] The SMF is responsible for establishing, maintaining, and terminating Protocol Data Unit sessions in core network 108. The SMF manages user plane resources and interacts with the UPF in core network 108 to ensure that data packets are correctly routed and forwarded.

[0061] The UDM performs the authentication process, stores and manages user data (including subscriber profiles, authentication certificates, and authorization policies), implements security mechanisms to protect user data and resources of the communication network (e.g., core network 108) from unauthorized access attacks and vulnerabilities, and interacts with other network functions of the core network 108 (such as PCF) to enforce access control policies, Quality of Service (QoS) parameters, and service restrictions based on user profiles and subscription plans. The UDM is also responsible for managing the registration of network functions 110 serving user equipment 100.

[0062] The PCF provides a generic (URSP) to the user equipment (e.g., user equipment 100) that includes one or more URSP rules. Each corresponding URSP rule includes a service descriptor (TD) and an RSD, whereby the RSD indicates the attributes of the data session of the application's service. Thus, each corresponding URSP rule indicates the set of attributes of the data session through which the application's service is sent, where the set of attributes includes one or more attributes.

[0063] Figure 3 The physical and logical components of an exemplary device 300 according to an implementation of this disclosure are shown. This device includes one or more network functions 110 of a communication network 104, including a CSAF. Although an example implementation of device 300 is shown and discussed below, other devices may include network functions 110 of a communication network (e.g., network functions of a core network), including the CSAF disclosed herein, and other devices may include [other functions related to...]. Figure 3 The different physical and logical components are shown. Furthermore, although... Figure 3 A single instance of each component of device 300 is shown, but Figure 3 Each logical or physical component shown can have multiple instances.

[0064] Device 300 includes one or more processors 302, such as a central processing unit (CPU), microprocessor, application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), application-specific logic circuit system, graphics processing unit (GPU), tensor processing unit, neural processing unit, dedicated artificial intelligence processing unit, hardware accelerator, or a combination thereof. One or more processors 302 may generally be referred to as processor 302, and are collectively referred to as processor 302.

[0065] Device 300 also includes one or more memories 304 (generally referred to as memory 304, and collectively referred to herein as "memory 304"), which may include volatile or non-volatile memory (e.g., flash memory, random access memory (RAM), and / or read-only memory (ROM)). Memory 304 may store computer code (e.g., instructions) for one or more network functions executed by at least one of one or more processors 302. For example, computer code (e.g., instructions) 306 of the CSAF described herein is shown as stored in memory 304, wherein the computer code (e.g., instructions), when executed by at least one of one or more processors 302, causes device 300 to perform the operations of the CSAF described herein. Memory 304 may store machine-executable instructions for execution by processor 104, such as those referenced above. Figure 1 Machine-executable instructions for other network functions of the core network 108 (e.g., other core network functions such as SMF, AMF, NSSF, PCF, UDM entities, NRF, and NSACF).

[0066] In addition to executable instructions 306, memory 304 may also store data, information, rules and / or policies.

[0067] In some examples, device 300 may also include one or more electronic storage units (not shown), such as solid-state drives, hard disk drives, disk drives, and / or optical disk drives. In some examples, one or more datasets and / or modules may be provided by external memory (e.g., an external drive that is wired or wirelessly connected to computing system 100), or by transient or non-transitory computer-readable media. Examples of non-transitory computer-readable media include RAM, ROM, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, CD-ROM, or other portable storage. Storage units and / or external memory may be used in conjunction with memory 112 to enable data storage, retrieval, and caching functions of device 300.

[0068] For example, the processor and memory 304 of device 300 can communicate with each other via a communication bus.

[0069] In some implementations, device 300 is a single physical computing device. In some implementations, device 300 is a distributed computing system comprising multiple computing devices (e.g., servers) communicating with each other via a data network, and optional one or more additional components. In some embodiments, the various operations described herein may be performed by different computing devices (e.g., servers) of the distributed computing system. In some implementations, device 300 is a virtual machine provided by the infrastructure (e.g., hypervisor, processor, and memory) of a cloud computing system. In some implementations, network functions 110 (such as CSAF, AMF, SMF, PCF, etc.) are implemented as virtual machines or containers on the cloud computing system.

[0070] The network function 110 of core network 108 is referred to herein as core network function 110. Furthermore, any core network function 110 can be implemented as a core network entity (also referred to as a core network entity), which includes a combination of hardware processing circuitry and software and / or firmware, comprising machine-readable instructions, or software comprising machine-readable instructions executable by at least one processor of the hardware processing circuitry of a computing device or system. The hardware processing circuitry includes one or more processors and one or more memories storing machine-readable instructions. The one or more processors include any one or a combination of an accelerator, microprocessor, multi-core microprocessor core, microcontroller, programmable integrated circuit, programmable gate array, digital signal processor, central processing unit, graphics processing unit, tensor processing unit, and quantum processing unit. The one or more memories include any one or a combination of volatile or non-volatile memories (e.g., flash memory, cache, random access memory (RAM), and / or read-only memory (ROM)). The memories store machine-readable instructions of the software and / or firmware for execution by at least one processor of the hardware processing circuitry. Machine-readable instructions can be executed by at least one processor of the hardware processing circuitry to cause the hardware processing circuitry to perform the actions or operations of the methods described herein. For example, the session management functions described herein can be implemented as a session management entity, and the session management policy control functions described herein can be implemented as a session management policy control entity.

[0071] As used herein, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuit systems only) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor (including multiple digital signal processors), software, and memory (multiple processors), which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to function, but may be absent when not in use.

[0072] refer to Figure 4 An example of a communication device 100 is shown. Although Figure 4 A single instance of each physical and logical component of the communication device 100 is shown, but the communication device 100 may include multiple instances of each physical or logical component shown.

[0073] Communication device 100 can be any device capable of transmitting and receiving wireless signals (e.g., wireless signals). Non-limiting examples of communication devices include user equipment (UE), mobile station (MS) or mobile terminal (MT), such as cellular phones, mobile phones or so-called 'smartphones', computers equipped with wireless interface cards or other wireless interface facilities (e.g., USB dongles), wearable devices (such as smartwatches, personal data assistants (PDAs) or tablets equipped with wireless communication capabilities), machine-type communication (MTC) devices, Internet of Things (IoT) type communication devices, or any combination of these devices.

[0074] The communication device 100 also includes one or more processors 401, one or more memories 402 (collectively referred to as memory 402), and other components or circuit systems 403 for software and hardware-assisted execution of operations configured to be performed by the user equipment 100, including access to a wireless access network (e.g., Figure 1 The processor 401 controls access to and communication with RAN 106 (shown). Processor 401 is coupled to memory 402. One or more processors 401 may include a central processing unit (CPU), microprocessor, multi-core processor, tensor processing unit (TPU), graphics processing unit (GPU), neural processing unit (NPU), application-specific logic circuit, application-specific integrated circuit, field-programmable gate array (FPGA), dedicated artificial intelligence processing unit, hardware accelerator, or any combination thereof. Memory 402 may include volatile or non-volatile memory (e.g., flash memory, random access memory (RAM), and / or read-only memory (ROM)).

[0075] Processor 401 may be configured to execute computer code 408 (e.g., the processor may execute the instructions of computer code 408). Execution of computer code 408 (or execution of the instructions of the computer code) may, for example, cause user equipment 100 to perform one or more operations, including those described herein. Figure 11 The operation described above. Computer code 408 can be stored in memory 402.

[0076] User equipment 100 also includes an antenna array 404 and a transceiver 406 for transmitting (e.g., wireless signals) wireless signals to and / or receiving wireless signals from access nodes of the access network (e.g., RAN nodes of the RAN) via an air interface 407 (e.g., wireless signals). The wireless signals may carry communications such as voice, email, text messages, multimedia data, and / or machine data. The antenna array 406 may be disposed inside or outside the user equipment 100. The antenna array 406 may include one or more antenna elements. The antenna array 406 may be a multiple-input multiple-output (MIMO) antenna.

[0077] The processor 401, at least one memory 402, transceiver 406, and other components or circuitry 403 of user equipment 100 (e.g., a modem) may be disposed on a circuit board, in a chipset, or in a system-on-a-chip (SOC). The circuit board, chipset, or SOC may be disposed on... Figure 3 The reference numeral 404 indicates the device. User equipment 100 may optionally include a display device 405, such as a touch-sensitive display device. User equipment 100 also includes a battery (not shown). Communication equipment 100 may also include a speaker (not shown) and a microphone (not shown). Communication equipment 100 may also include a Universal Subscriber Identity Module (USIM) (not shown) or an Embedded Subscriber Identity Module (eSIM) (not shown). In order for a communication device (e.g., UE) to send (e.g., report) information to the CSAF of the communication network, an association needs to be established between the communication device and the CSAF.

[0078] Now for reference Figure 5This illustrates a first procedure for establishing communication between a UE (e.g., UE 100) and a CSAF of a communication network. The first procedure for establishing communication between a UE (e.g., UE 100) and a CSAF of a communication network involves the user equipment (e.g., UE 100) and the AMF and CSAF of the communication network (e.g., the core network of the communication network, such as core network 108), and includes control plane signaling (e.g., control plane messages) transmitted between the UE (e.g., UE 102), the AMF, and the CSAF, as well as operations performed by the AMF to create an association between the UE (e.g., UE 100) and the CSAF.

[0079] The first process is part of the UE registration process (e.g., it occurs during the UE's (e.g., UE 100) registration with the communication network). The first process begins at point 1. At point 1, the UE (e.g., UE 100) determines to register with the communication network (e.g., determines to register with the core network 108 of the communication network) and sends a request to the AMF of the communication network (e.g., the AMF of the core network 108 of the communication network) to register with the communication network. The request to register with the communication network is referred to herein as a registration request and includes an indication that instructs the UE to request the establishment of a communication channel with the CSAF (or an indication that instructs the UE to request to report a service descriptor (referred to herein as a TD report) to the CSAF and / or an indication that instructs the UE (e.g., UE 100) to support communication with the CSAF of the communication network (e.g., UE 100 is configured to communicate with the CSAF or is capable of communicating with the CSAF). In some implementations, the registration request includes an indication that instructs the UE (e.g., UE 100) to associate with the CSAF.

[0080] At point 2, upon receiving a registration request from the UE (e.g., UE 100), the AMF triggers (e.g., causes or instructs) the UDM via the AUSF to initiate an authentication process for the UE. As a result of the AMF triggering the UDM via the AUSF, a UE authentication process is performed, involving the UDM, AUSF, AMF, and UE. The executed UE authentication process follows the guidelines in 3GPP TS 33.501V18.0.0. Figure 6 1.2-1、 Figure 6 1.3.1-1 and Figure 6 As shown in .1.3.2-1.

[0081] At three points, based on an indication that the UE (e.g., UE 100) supports communication with the CSAF, the AMF selects the CSAF using location information indicating the UE's location, parameters of the UE's UE context, and subscriber information corresponding to the UE's subscriber. Examples of parameters of the UE's UE context include the aggregated maximum bit rate of the UE's subscription, the identifier of the network slice the UE subscribes to (referred to herein as the UE's subscription S-NSSAI), the UE's usage type, the UE's Closed Access Group Information (CAG) (including the CAG identifier), whether the UE can access communication via CAG cells only (e.g., PLMN), the UE's Radio Access Technology (RAT) / Frequency Part Priority Index, and the Multimedia Priority Service (MPS) priority.

[0082] At point 4, the AMF invokes the service of the CSAF selected at point 3 via the Ncsaf interface and sends a request to the selected CSAF at point 3 to establish an association between the UE and the CSAF. The CSAF establishes the association between the UE and the CSAF based on the receipt of the request, indicating that communication between the UE and the CSAF is established; a response to the request is sent via the Ncsaf interface, indicating that the association between the UE and the CSAF has been established by the CSAF. During the first procedure, the CSAF may provide a list of service descriptors, including one or more service descriptors (TDs) that the UE can provide to the CSAF (e.g., report or send).

[0083] At point 5, the AMF sends a response to the registration request sent by the UE at point 1. The response to the registration request is a registration acceptance message, which indicates that the registration request sent by the UE has been accepted by the communication network, and that the UE registers with the communication network. In some implementations, the response includes a list of service descriptors (TDs), which includes one or more service descriptors (TDs) that the UE can provide (e.g., report or send) to the CSAF, and optional CSAF addressing information. In some implementations, the response includes an indication indicating whether the UE is permitted to communicate with the CSAF, and when the response includes an indication indicating that the UE is permitted to communicate with the CSAF, the response also includes a list of TDs and optional CSAF addressing information. The CSAF addressing information includes the CSAF identifier and Internet Protocol address or CSAF. After the first process is completed at point 5, the UE (e.g., UE 100) can provide (e.g., report or send) a TD to the CSAF. For example, the UE can provide (e.g., report or send) a TD to the CSAF when the TD has started to be used by the UE, or when the TD has stopped being used by the UE, as follows regarding... Figure 7Further detailed description. In addition to providing (e.g., reporting or sending) TD to the CSAF, the UE may also provide (e.g., reporting) UE capability information. UE capability information may include information indicating the maximum number of data sessions supported by the UE and information indicating the data session attributes supported by the UE. UE capability information may include other information about the UE's capabilities. Other information about the UE's capabilities includes one or more of the following: information indicating that the UE supports Reflective Quality of Service (RQoS); information indicating that the UE supports multi-homed IPv6 PDU sessions; information indicating that the UE supports Access Service Bootstrapping, Handover and Split (ATSSS) bootstrapping functions and bootstrapping modes; information indicating that the UE supports the transmission of port management information containers; information indicating that the UE supports access performance measurements according to QoS flow rules (e.g., for the corresponding QoS flow rules); or information indicating that the UE supports secondary data network authentication and authorization on the Evolved Packet Core (EPC).

[0084] Now for reference Figure 6 This illustrates an example of a second process for establishing communication between a UE (e.g., UE 100) and the CSAF of a communication network. This second process for establishing communication between a UE (e.g., UE 100) and the CSAF of a communication network (referred to as the second UE CSAF association creation process) involves the user equipment (e.g., UE 100) and the AMF and CSAF of the communication network (e.g., the core network of the communication network, such as core network 108), and includes control plane signaling (e.g., control plane messages) transmitted between the UE (e.g., UE 102), the AMF, and the CSAF, as well as operations performed by the AMF to create an association between the UE (e.g., UE 100) and the CSAF.

[0085] The second process begins at point 1. At point 1, the UE (e.g., UE 100) sends an uplink non-access stratum transport message (such as...) to the AMF of the communication network. Figure 6 (As shown in UL NAS TRANSPORT). In some implementations, the uplink non-access stratum transport message includes an indication of the payload type of the uplink non-access stratum transport message's payload, as well as a payload including the message initiated when delivered from the UE to the CSAF. This message is referred to herein as a Connection Service Management (CSA) message. The payload type indication indicates that the payload of the uplink non-access stratum transport message includes a message to be delivered by the AMF to the CSAF (e.g., a CSA message). In some implementations, the uplink non-access stratum transport message includes information identifying that the payload of the uplink non-access stratum transport message is to be delivered to the CSAF, as well as a payload including a message to be delivered by the AMF to the CSAF (e.g., a Connection Service Management (CSA) message).

[0086] At point 2, after receiving the uplink non-access stratum transmission message, the AMF selects the CSAF to associate with the UE based on location information indicating the UE's location, UE context parameters, and subscriber information corresponding to the UE's subscriber. Examples of UE context parameters include the UE's subscribed aggregate maximum bit rate, the identifier of the network slice the UE subscribes to (referred to herein as the UE's subscribed S-NSSAI), the UE's usage type, the UE's Closed Access Group (CAG) information (including the CAG identifier and whether the UE can access communication via CAG cells only (e.g., PLMN)), the UE's Radio Access Technology (RAT) / Frequency Band Priority Index, and Multimedia Priority Service (MPS) priority.

[0087] At point 3, the AMF invokes the CSAF's service via the Ncsaf interface and sends a request to the CSAF selected at point 2 to establish an association between the UE and the CSAF (e.g., the CSAF sends an Ncsaf_UE_association request to the CSAF). The request to establish an association between the UE and the CSAF (e.g., the Ncsaf_UE_association request) includes a CSA message in the payload of the uplink non-access stratum transport message received by the AMF. Based on the received request to establish an association between the UE and the CSAF (e.g., the Ncsaf_UE_association request), the CSAF establishes the association between the UE and the CSAF (e.g., based on the received CSA message included in the Ncsaf_UE_association request).

[0088] At point 4, after the CSAF establishes an association between the UE and the CSAF, the CSAF sends a response to the AMF regarding the request to establish the association between the UE and the CSAF (e.g., an Ncsaf_UE_association response). The response to the request to establish the association between the UE and the CSAF (e.g., the Ncsaf_UE_association response) includes a message to be sent by the AMF to the UE. The message to be sent by the AMF to the UE includes a list of service descriptors (TDs). The TD list includes one or more service descriptors (TDs) that the UE can provide to the CSAF (e.g., report or send).

[0089] At point 5, after receiving the Ncsaf_UE_association response, the AMF sends a downlink non-access stratum transport message (such as...) to the UE. Figure 6(As shown in DL NAS TRANSPORT). Downlink non-access stratum transport messages include messages (including a list of service descriptors). In some implementations, the messages in the downlink non-access stratum transport messages include a list of service descriptors, which includes one or more service descriptors (TDs) that the UE can provide (e.g., report or send) to the CSAF, and optional CSAF addressing information. In some implementations, the messages in the downlink non-access stratum transport messages include an indication of whether the UE is permitted to communicate with the CSAF, and when the response includes an indication of whether the UE is permitted to communicate with the CSAF, the downlink non-access stratum transport message also includes a list of TDs and optional CSAF addressing information.

[0090] After completing the second UE CSAF creation process at point 5, the UE (e.g., UE 100) can provide (e.g., report or send) a TD to the CSAF. For example, the UE can provide (e.g., report or send) a TD to the CSAF by sending an indication when the TD has started to be used by the UE or when the TD has stopped being used by the UE, as follows regarding... Figure 7 In addition to providing (e.g., reporting or sending) TDs to the CSAF, the UE may also provide (e.g., reporting) UE capability information. UE capability information may include information indicating the maximum number of data sessions (e.g., PDU sessions) supported by the UE (e.g., information indicating the maximum number of data sessions the UE can establish), information indicating that the UE supports multihomed IPv6 data sessions, and information about other UE capabilities.

[0091] In some examples, a UE registered to the network provides one or more Data Session Attributes (TDs) for use by the UE to the CSAF via the user plane of the communication network. In some examples, a UE registered to the network provides one or more TDs for use by the UE to the CSAF via the control plane. After receiving one or more TDs, the CSAF determines one or more data session attribute sets and sends the one or more data session attribute sets to the UE or an NF (e.g., an AMF or SMF) in the communication network. Each of the one or more data session attribute sets is associated with one or more TDs. Based on the received data session attributes and TDs, the UE or the NF in the communication network initiates the establishment, modification, or release of one or more data sessions. The CSAF may be co-located with another NF (e.g., an AMF, PCF, NSSF) on a device (such as device 300), or the functionality of the CSAF may be part of another NF, such as the AMF, PCF, or NSSF of the communication network.

[0092] Now for reference Figure 7This illustrates the process for establishing a network-initiated data session (referred to herein as the network-initiated data session establishment process). During the network-initiated data session establishment process, the CSAF determines the data session attributes of the new data session and sends the determined data session attributes to the SMF, which then initiates the establishment of the new data session. Figure 7 The network-initiated data session establishment process shown involves the UE (e.g., UE 100), the RAN node of the RAN (e.g., RAN node), the CSAF, the SMF, and the UPF of the communication network (e.g., the UPF of core network 108). For ease of explanation, Figure 7 The AMF is not shown. However, it should be understood that control plane signaling (e.g., control plane messages) transmitted between the CSAF and the UE, and between the SMF and the UE, is transmitted via the AMF and the RAN node.

[0093] The network-initiated data session establishment process begins at point 1. At point 1, the UE provides the CSAF with a service descriptor that has already been used by the UE. In some implementations, the UE provides an identifier for the service descriptor that has already been used by the UE. In some implementations, the UE can provide the service descriptor that has already been used by the UE when it detects that an application on the UE has been started. In some implementations, the UE can provide the service descriptor that has already been used by the UE when it determines that an application running on the UE requires a new type of service. In some implementations, the UE (e.g., UE 100) provides (e.g., reports or sends) the service descriptor that has already been used by the UE to the CSAF by sending a control plane message, which includes an identifier for the service descriptor that has already been used by the UE. In some implementations, the UE assigns a data session identifier to identify the data session of the service described by the service descriptor and provides (e.g., sends) the data session identifier to the CSAF. In some implementations, the UE can provide the service descriptor that has already been used by the UE and the data session identifier assigned to the CSAF by the UE by sending a control plane message, which includes the service descriptor that has already been used by the UE and the data session identifier assigned by the UE.

[0094] At point 2, after receiving a service descriptor that has already been used by the UE, the CSAF determines to establish a new data session for the service described by the service descriptor. The CSAF also determines a set of data session attributes for the new data session of the service described by the service descriptor. The set of data session attributes includes at least one of the following: the session type of the new data session; the session and service concentration and continuity (SSC) mode; the identifier of the network slice on which the new data session is to be established; or the data network name of the data network on which the data session terminates. The session type of the new data session can be an Internet Protocol version 4 (IPv6) data session, an IPv6 and IPv6 data session, an unstructured data session, or an Ethernet data session. In some implementations, the CSAF determines the set of data session attributes for the new data session of the service described by the service descriptor based on information about the UE's capabilities (generally referred to herein as the UE's UE capabilities) and information obtained from other entities in the communication network. The information about the capabilities of a user equipment (UE) used by the CSAF to determine the set of data session attributes for a new data session includes one or more of the following: information indicating the maximum number of data sessions supported by the UE; information indicating the data session attributes supported by the UE, and other information about the UE's capabilities; information indicating that the UE supports Reflective Quality of Service (RQoS); information indicating that the UE supports multihomed IPv6 PDU sessions; information indicating that the UE supports Access Service Bootstrapping, Handover, and Split (ATSSS) bootstrapping functionality and bootstrapping modes; information indicating that the UE supports the transmission of port management information containers; information indicating that the UE supports access performance measurements based on QoS flow rules (e.g., for the corresponding QoS flow rules); or information indicating that the UE supports secondary data network authentication and authorization on the Evolved Packet Core (EPC). Information obtained from the entities of the communication network used by CSAF to determine the attribute set includes one or more of the following: information indicating the location of the user equipment; information indicating the resource status of the radio access network of the communication network; identification of network slices supported by the radio access network of the communication network; subscription information of the subscriber associated with the user equipment; information indicating the access type of the access network through which the user equipment registers with the communication network; network slice restriction information; network slice replacement information; information indicating the resource status of the session management function of the communication network; or information indicating the identification of network slices supported by the session management function.

[0096] At point 3, CSAF performs SMF selection to choose an SMF based on the set of data session attributes determined at point 2.

[0097] At point 4, the CSAF requests the SMF selected at point 3 to create a new Session Management (SM) context for the new data session. In other words, at point 4, the CSFA sends a request to create a new SM context for the new data session via the Nsmf interface. In some implementations, the request to create a new SM context for the new data session may be an Nsmf_DataSessionCreateSMContext request.

[0098] At point 5, a data session establishment process is performed, which involves the selected SMF and UPF to establish a new data session for the service described by the service descriptor.

[0099] At point 6, after completing the data session establishment process, SMF sends a response via the Nsmf interface to the request to create a new SM context for the new data session. In some implementations, the response to the request to create a new SM context for the new data session may be an Nsmf_DataSessionCreateSMContext response.

[0100] At point 7, the CSAF sends an N2 Connection and Management (CSA) command to the RAN via the AMF. This command includes Session Management (SM) information and a request to establish a new data session (referred to herein as a Data Session Establishment Request).

[0101] At 8 locations, access layer (AS) resources are established between the RAN node and the UE based on the session management (SM) information of the RAN node.

[0102] At point 9, after or during AS resource establishment, the RAN node extracts the data session establishment request from the N2 CSA command, and after AS resource establishment is complete, the RAN node forwards the data session establishment request to the UE. In some implementations, the data session establishment request includes one or more of the following: a data session identifier assigned to the new data session, a set of data session attributes, and quality of service (QoS) information for the data session, bit rate information indicating the maximum bit rate of the data session, an Internet Protocol (IP) address, or an interface identifier identifying the interface used in the data session (e.g., Ethernet).

[0103] At point 10, the RAN node receives a data session establishment response from the UE. The data session establishment response is a response to a request to establish a new data session for the service described by the service descriptor.

[0104] At point 11, after receiving the data session establishment response, the RAN node sends an N2 CAS completion message to the CSAF via the AMF. The CAS completion message includes tunnel information for the tunnel between the RAN node and the UPF. The tunnel between the RAN node and the UPF is part of a new data session established for the service described by the service descriptor. The new data session is conducted between the UE and the UPF via the RAN node. The tunnel information includes the Internet Protocol addresses of the UE and the UPF.

[0105] At point 12, the CSAF sends the tunnel information received from the RAN node to the selected SMF. In some implementations, the CSAF provides the tunnel information to the selected SMF by, for example, sending a control plane message that includes the tunnel information.

[0106] At point 13, the SMF provides (e.g., sends) tunnel information to the UPF.

[0107] Now for reference Figure 8 This illustrates the procedure for network-initiated data session modification (referred to herein as the network-initiated data session modification procedure). The network-initiated data session modification procedure involves the UE (e.g., UE 100), the RAN node of the RAN (e.g., RAN node), the CSAF, the SMF, and the UPF of the communication network (e.g., the UPF of core network 108). For ease of explanation, Figure 8 The AMF is not shown. However, it should be understood that control plane signaling (e.g., control plane messages) transmitted between the CSAF and the UE, and between the SMF and the UE, is transmitted via the AMF and the RAN node.

[0108] The network-initiated data session modification process begins at point 1. At point 1, the UE provides the CSAF with a service descriptor that has already been used by the UE. In some implementations, the UE provides an identifier for the service descriptor that has already been used by the UE. In some implementations, the UE can provide a service descriptor that has already been used by the UE when it detects that an application running on the UE has been started. In some implementations, the UE can provide a service descriptor that has already been used by the UE when it determines that an application running on the UE requires a new type of service. In some implementations, the UE (e.g., UE 100) provides (e.g., reports or sends) an indication and an identifier of the service descriptor that has already been used by the UE to the CSAF by sending a control plane message, which includes the indication and the identifier of the service descriptor. In some implementations, the UE may also provide an identifier of the data session that the UE requests to be modified.

[0109] At point 2, after receiving a service descriptor that has already been used by the UE, the CSAF determines that the existing data session for the service described by the service descriptor needs to be modified. The CSAF also determines a set of data session attributes for the existing data session of the service described by the service descriptor. The set of data session attributes includes at least one of the following: the session type of the new data session, the session and service concentration and continuity (SSC) mode; the identifier of the network slice on which the data session is to be established; or the data network name of the data network on which the data session terminates. The session type of the new data session can be an Internet Protocol version 4 (IPv6) data session, an IPv6 and IPv6 data session, an unstructured data session, or an Ethernet data session. The CSAF may determine the set of data session attributes for the existing data session of the service described by the service descriptor based on information about the UE's capabilities and information obtained from other entities in the communication network.

[0110] In three places, the CSAF identifier serves the SMF of the existing data session.

[0111] At point 4, the CSAF requests the SMF selected at point 3 to create a new Session Management (SM) context for the existing data session. In other words, at point 4, the CSFA sends a request to create a new SM context for the existing data session via the Nsmf interface. In some implementations, the request to create a new SM context for the existing data session may be an Nsmf_DataSessionCreateSMContext request.

[0112] At point 5, a data session modification process is performed, which involves the identified SMF and UPF to modify the new existing session for the service described by the service descriptor based on the data session attribute set determined at point 2.

[0113] At point 6, after completing the data session modification process, SMF sends a response via the Nsmf interface to the request to create a new SM context for the existing data session. In some implementations, the response to the request to create a new SM context for the existing data session may be an Nsmf_DataSessionCreateSMContext response.

[0114] At point 7, the CSAF sends an N2 Connection and Management (CSA) command to the RAN via the AMF. This command includes Session Management (SM) information and a request to modify an existing data session (referred to herein as a Data Session Modification Request).

[0115] At 8 locations, access layer (AS) resources are established between the RAN node and the UE based on the session management (SM) information of the RAN node.

[0116] At point 9, after or during AS resource establishment, the RAN node extracts the data session modification request from the N2 CSA command, and after AS resource establishment is complete, the RAN node forwards the data session modification request to the UE. In some implementations, the data session modification request includes one or more of the following: the data session identifier of the existing data session, the data session attribute set, and the quality of service (QoS) information of the data session, bit rate information indicating the maximum bit rate of the existing data session, the Internet Protocol (IP) address, or an interface identifier (e.g., Ethernet) identifying the interface used in the existing data session.

[0117] At point 10, the RAN node receives a data session modification response from the UE. The data session modification response is a response to a request to modify an existing data session for a service described by the service descriptor.

[0118] At point 11, after receiving the data session modification response, the RAN node sends an N2 CAS completion message to the CSAF via the AMF. The CAS completion message includes tunnel information for the tunnel between the RAN node and the UPF. The tunnel between the RAN node and the UPF is part of an existing data session established for the service described by the service descriptor. The existing data session is conducted between the UE and the UPF via the RAN node.

[0119] At point 12, the CSAF sends the tunnel information received from the RAN node to the selected SMF. In some implementations, the CSAF provides the tunnel information to the selected SMF by, for example, sending a control plane message that includes the tunnel information.

[0120] At point 13, the SMF provides (e.g., sends) tunnel information to the UPF.

[0121] Now for reference Figure 9 This illustrates the procedure for network-initiated data session release (referred to herein as the network-initiated data session release procedure). The network-initiated data session release procedure involves the UE (e.g., UE 100), the RAN node of the RAN (e.g., RAN node), the CSAF, the SMF, and the UPF of the communication network (e.g., the UPF of core network 108). For ease of explanation, Figure 9 The AMF is not shown. However, it should be understood that control plane signaling (e.g., control plane messages) transmitted between the CSAF and the UE, and between the SMF and the UE, is transmitted via the AMF and the RAN node.

[0122] The network-initiated data session release procedure begins at point 1. At point 1, the UE provides the CSAF with a service descriptor that has been discontinued by the UE. In some implementations, the UE provides an identifier for the service descriptor that has been discontinued by the UE. In some implementations, the UE can provide the service descriptor that has been discontinued by the UE when it detects that an application on the UE has been turned off or terminated. In some implementations, the UE (e.g., UE 100) provides (e.g., reports or sends) the service descriptor that has been discontinued by the UE to the CSAF by sending a control plane message, which includes an identifier for the service descriptor that has been discontinued by the UE. At point 2, after receiving the service descriptor that has been discontinued by the UE, the CSAF identifies that it is serving a data session for the service descriptor that has been discontinued by the UE.

[0123] At point 3, after the CSAF identifies a data session that is serving a service descriptor that has been discontinued by the UE, the CSAF identifies the SMF that is serving the identified data session.

[0124] At point 4, after the CSAF identifies the SMF serving the identified data session, the CSAF requests the SMF identified at point 3 to update the Session Management (SM) context of the data session identified at point 2. In other words, at point 4, the CSAF sends a request to update the SM context of the data session identified at point 3 via the Nsmf interface. In some implementations, the request to update the SM context of the data session may be an Nsmf_DataSessionUpdateSMContext request.

[0125] At point 5, a data establishment release is performed, which involves the selected SMF and UPF to release data sessions that have been terminated by the service descriptor used by the UE (e.g., data sessions serving the service descriptor identified at point 2).

[0126] At point 6, after completing the data session release process, SMF sends a response via the Nsmf interface to the request to update the SM context of the data session. In some implementations, the response to the request to update the SM context of the data session may be an Nsmf_DataSessionUpdateSMContext response.

[0127] At point 7, the CSAF sends an N2 Connection and Management (CSA) command to the RAN via the AMF, which includes a request to release a data session (referred to herein as a data session release request).

[0128] At point 8, an access stratum (AS) resource modification occurs between the RAN node and the UE to release the AS resources of the data session being released.

[0129] At point 9, after or during AS resource establishment, the RAN node extracts a data session release request from the N2 CSA command, and after the AS resource modification is complete, the RAN node forwards the data session release request to the UE. In some implementations, the data session release request includes the data session identifier of the data session to be released.

[0130] At point 10, the RAN node receives a data session release response from the UE. The data session release response is a response to a request to release a data session serving a service descriptor that has ceased to be used by the UE.

[0131] At point 11, after receiving the data session release response, the RAN node sends an N2 CAS complete message to the CSAF via the AMF. The CAS complete message indicates to the CSAF that the release of the data session serving the service descriptor that has been discontinued by the UE has been completed.

[0132] Now for reference Figure 10 The diagram illustrates a flowchart of method 1000 according to an example implementation. Method 1100 may be performed or carried out by a first core network entity, such as a network entity configured for communication and service management of a communication network. The first core network entity may implement a first core network function, such as the CASF described herein. Alternatively, the first core network entity may implement another core network function, such as AMF or SMF, which includes the functionality of the CASF described herein. Method 1100 includes operations 1002 through 1006. However, the method may include additional or fewer operations, and the other operations may occur in any suitable order.

[0133] The method begins at position 1002. At position 1002, the first network entity receives from the user equipment a service descriptor that has begun to be used by the user equipment. In some implementations, the first network entity receives an identifier of the service descriptor from the UE, which identifies the service descriptor that has begun to be used by the user equipment.

[0134] At point 1004, the first core network entity determines the set of data attributes for the service described in the service descriptor based on information about the capabilities of the communication equipment and information obtained from other core network entities of the communication network. In some implementations, the data session attributes include at least one of the following: the session type of the data session, where the session type includes Internet Protocol version 4 (IPv6) data session, Internet Protocol version 4 (IPv6) data session, IPv6 and IPv6 data session, unstructured data session, or Ethernet data session; the session and service continuity (SSC) mode; an identifier for the network slice on which the data session is to be established or modified; or the data network name of the data network on which the data session terminates. In some implementations, the first network entity determines the set of data session attributes by: determining multiple sets of data session attributes corresponding to the service descriptor based on a mapping that associates the service descriptor with multiple sets of data session attributes; and selecting a set of data session attributes from the multiple sets of data session attributes based on information about the capabilities of the user equipment and information obtained from entities of the communication network. In some implementations, determining multiple sets of data session attributes includes: retrieving from a database a mapping that associates the service descriptor with multiple sets of data session attributes.

[0135] In some implementations of method 199, the information obtained from entities of the communication network includes at least one of the following: information indicating the location of the user equipment; information indicating the resource status of the radio access network of the communication network; an identifier of a network slice supported by the radio access network of the communication network; subscription information of a subscriber associated with the user equipment; information indicating the access type of the access network through which the user equipment has registered with the communication network; network slice restriction information; network slice replacement information; information indicating the resource status of the session management function of the communication network; or information indicating the identifier of a network slice supported by the session management function.

[0136] In some implementations, information regarding the capabilities of a user equipment includes at least one of the following: information indicating the maximum number of data sessions supported by the user equipment; information indicating the attributes of the data sessions supported by the user equipment, and other information regarding the capabilities of the user equipment; information indicating that the user equipment supports Reflective Quality of Service (RQoS); information indicating that the user equipment supports multihomed IPv6 PDU sessions; information indicating that the user equipment supports Access Service Bootstrapping, Handover, and Split (ATSSS) bootstrapping functionality and bootstrapping modes; information indicating that the user equipment supports the transmission of port management information containers; information indicating that the user equipment supports access performance measurement based on QoS flow rules; or information indicating that the user equipment supports secondary data network authentication and authorization on the Evolved Packet Core (EPC).

[0137] At point 1006, the first core network entity provides a set of data session attributes to the second core network entity or user equipment. This set is determined by the second core network entity or user equipment and is used to establish a new data session for a service described by a service descriptor or to modify an existing data session for a service described by a service descriptor.

[0138] In some implementations, the first core network entity also performs the following actions: establishing new data sessions or modifying existing data sessions based on a data session attribute set. Specifically, the first core network entity establishes a new data session by sending a data session establishment request to the user equipment. This data session establishment request includes at least one of the following: a data session identifier identifying the new data session, quality of service information indicating the quality of service of the data session, bit rate information indicating the maximum bit rate of the data session, and an Internet Protocol (IP) address. Alternatively, the first core network entity modifies an existing data session by sending a data session modification request to the user equipment. This data session modification request includes at least one of the following: a data session identifier identifying the new data session, quality of service information indicating the quality of service of the data session, bit rate information indicating the maximum bit rate of the data session, and an IP address.

[0139] In some implementations, the first core network entity sends an instruction to the second core network entity or user equipment, which is configured to cause the second core network entity or user equipment to initiate the establishment of a data session or to initiate the modification of a data session based on a data session attribute set.

[0140] In some implementations, the first core network entity selects the session management function of the communication network to establish or modify a data session using a data session attribute set; it sends a request to the session management function to create a session management context for the data session, wherein the request includes a data session identifier assigned to the data session. The first core network entity also receives the session management context of the data session from the session management function and provides the session management context and the data session identifier assigned to the data session to the radio access network nodes of the communication network.

[0141] In some implementations, the first core network entity receives an identifier associated with information about the capabilities of the user equipment (UE) from the UE, and uses the identifier associated with the information about the UE's capabilities to retrieve the UE's information capabilities.

[0142] In some implementations, the first core network entity receives a response from the user equipment to the transmission of instructions, indicating the success or failure of the establishment or modification of a data session.

[0143] In some implementations, the first core network entity receives an indication from the user equipment that the service descriptor has ceased to be used by the user equipment; sends an instruction to the user equipment configured to cause the user equipment to request the release of the data session; and receives a release completion message from the user equipment indicating that the data session has been released.

[0144] In some implementations, the first core network entity receives from the user equipment an indication that the second service descriptor has ceased to be used by the user equipment; sends an instruction to the user equipment configured to cause the user equipment to request the release of a second data session for the service described by the second service descriptor; and receives from the user equipment a release completion message indicating that the release of the second data session is complete.

[0145] Now for reference Figure 11 The diagram illustrates a flowchart of method 1100 according to an example implementation. Method 1100 can be performed or carried out by a user equipment, such as UE 100 described herein. Method 1100 includes operations 1102 to 1106. However, the method may include additional or fewer operations, and other operations may occur in any suitable order.

[0146] The method begins at step 1102. At step 1102, the UE sends a service descriptor that has begun to be used by the user equipment to the first core network entity of the communication network. In some implementations, the UE sends the service descriptor that has begun to be used by the UE after detecting that the service descriptor has begun to be used.

[0147] At 1104, the UE receives a data session attribute set from the first core network entity. The data session attribute set will be used to establish a new data session for a service described by a service descriptor or to modify an existing data session for a service described by a service descriptor.

[0148] At point 1106, the UE initiates the establishment of a new data session or the modification of an existing data session with a data session attribute set. In some implementations, based on instructions received from a first core network entity or a second core network entity of the communication network, the UE initiates the establishment of a new data session or the modification of an existing data session based on a data session attribute set.

[0149] In some implementations, after initiating the establishment of a new data session or modifying an existing data session with a set of data session attributes, the UE detects the successful establishment or modification of the data session and sends a response to the instruction to the first core network entity, indicating the successful establishment or modification of the data session.

[0150] In some implementations, after initiating the establishment of a new data session or modifying an existing data session with a set of data session attributes, the UE detects the failure of the data session establishment or modification and sends a response to the instruction to the first core network entity, indicating the failure of the data session establishment or modification. The response indicating the failure of data session establishment or modification may include a reason value indicating the cause of the failure.

[0151] In some implementations, before sending the service descriptor that has already been used by the user equipment, the UE sends information about the user equipment's capabilities to the first core network entity to determine the data session attribute set. This information about the communication equipment's capabilities includes at least one of the following: information indicating the maximum number of data sessions supported by the user equipment; information indicating the data session attributes supported by the user equipment, and other information about the user equipment's capabilities; information indicating that the user equipment supports Reflective Quality of Service (RQoS); information indicating that the user equipment supports multi-homed IPv6 PDU sessions; information indicating that the user equipment supports Access Service Bootstrapping, Handover, and Split (ATSSS) bootstrapping functionality and bootstrapping modes; information indicating that the user equipment supports the transmission of port management information containers; information indicating that the user equipment supports access performance measurement according to QoS flow rules; or information indicating that the user equipment supports secondary data network authentication and authorization on the Evolved Packet Core (EPC).

[0152] In some implementations, before sending the service descriptor that has already been used by the user equipment, the UE sends an identifier associated with information about the capabilities of the communication network to the first core network entity, so that the first core network entity can use it to retrieve information about the capabilities of the communication network.

[0153] In some implementations, after the service descriptor has ceased to be used by the user equipment, the UE sends the service descriptor to the first core network entity. Then, the UE receives from the user equipment an instruction configured to cause the user equipment to request the release of the data session, and releases the data session. In some implementations, after releasing the data session, the UE sends a release completion message to the first core network entity indicating that the data session has been released.

[0154] In some implementations, the UE sends a second service descriptor that has been discontinued by the user equipment to a first core network entity, and receives an instruction from the first core network entity configured to cause the user equipment to request the release of a second data session for the service described by the second service descriptor. The UE also sends a release completion message to the first core network entity indicating that the release of the second data session is complete.

[0155] In some implementations, the UE assigns a data session identifier (ID) to the data session and provides the data session ID to the first core network entity.

[0156] It should be noted that while an implementation has been described for 5G communication networks, similar principles can be applied to other communication networks, such as 6G communication networks. Therefore, although the example architecture of a 5G communication network has been described above in an illustrative manner, CSAF can be applied to any other suitable form of communication network besides those shown and described herein.

[0157] As used herein, the term "circuit system" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuit systems only) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor (including multiple digital signal processors), software, and memory (multiple processors), which work together to enable a device (such as a mobile phone or server) to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to function, but may be absent when not in use.

[0158] The independent claims define the scope of protection sought by the various exemplary implementations of this disclosure. Exemplary implementations and features (if any) described in this disclosure that are not within the scope of the independent claims shall be interpreted as examples that aid in understanding the various exemplary implementations of this disclosure.

[0159] The foregoing description provides a complete and informative description of various exemplary implementations of this disclosure by way of non-limiting and illustrative examples. However, various modifications and adaptations will be apparent to those skilled in the art when read in conjunction with the accompanying drawings and claims, given the foregoing description. Nevertheless, all such and similar modifications to these teachings will still fall within the various exemplary implementations of this disclosure as set forth in the claims. As a non-limiting and illustrative example, another exemplary implementation exists, comprising combinations of one or more exemplary implementations with any other exemplary implementations previously discussed.

Claims

1. A first core network entity of a communication network, the first core network entity comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the first core network entity to perform: Receive from the user equipment a service descriptor that has been initiated for use by the user equipment; Based on information about the capabilities of the user equipment and information obtained from entities in the communication network, a set of data session attributes for the service described by the service descriptor is determined; as well as The data session attribute set is provided to the second core network entity or the user equipment. The data session attribute set will be used to establish a data session for the service or to modify an existing data session for the service.

2. The first core network entity according to claim 1, wherein the instructions, when executed by the at least one processor, further cause the first core network entity to perform: Based on the data session attribute set, the process of establishing the new data session or modifying the existing data session is performed. The establishment of the new data session includes: Sending a data session establishment request to the user equipment to establish the new data session, the data session establishment request including at least one of the following: a data session identifier identifying the new data session, quality of service information for the quality of service of the data session, bitrate information indicating the maximum bitrate of the data session, and an Internet Protocol address, wherein performing the modification of the new existing session includes sending a data session modification request to the user equipment to modify the existing data session, the data session modification request including at least one of the following: a data session identifier identifying the new data session, quality of service information for the quality of service of the data session, bitrate information indicating the maximum bitrate of the data session, and an Internet Protocol address.

3. The first core network entity according to claim 1, wherein the instructions, when executed by the at least one processor, further cause the first core network entity to perform: Send an instruction to the second core network entity or the user equipment, the instruction being configured to cause the second core network entity or the user equipment to initiate the establishment of the data session or to initiate the modification of the data session based on the data session attribute set.

4. The first core network entity according to any one of claims 1 to 3, wherein the data session attribute set includes at least one of the following: the session type of the data session, wherein the session type includes Internet Protocol version 4 (IPv6) data session, Internet Protocol version 4 (IPv6) data session, IPv6 and IPv6 data session, unstructured data session or Ethernet data session; Session and Service Continuity (SSC) mode; the identifier of the network slice on which the data session is to be established or modified; Or the name of the data network to which the data session terminates; as well as The determination of the data session attribute set includes: determining the plurality of data session attribute sets corresponding to the service descriptor based on a mapping that associates the service descriptor with a plurality of data session attribute sets; and selecting the data session attribute set from the plurality of data session attribute sets based on information about the capabilities of the user equipment and information obtained from entities of the communication network; and The determination of the plurality of data session attribute sets includes: retrieving from a database the mapping that associates the service descriptor with the plurality of data session attribute sets; and The instructions, when executed by the at least one processor, further cause the first core network entity to perform: selecting a session management function of the communication network to establish or modify the data session using the data session attribute set; sending a request to the session management function to create a session management context for the data session, the request including a data session identifier assigned to the data session; receiving the session management context for the data session from the session management function; and providing the session management context for the data session and the data session identifier assigned to the data session to a radio access network node of the communication network; and The information obtained from the entities of the communication network includes at least one of the following: information indicating the location of the user equipment; information indicating the resource status of the radio access network of the communication network; an identifier of a network slice supported by the radio access network of the communication network; subscription information of a subscriber associated with the user equipment; information indicating the access type of the access network through which the user equipment has registered with the communication network; network slice restriction information; network slice replacement information; information indicating the resource status of the session management function of the communication network; or information indicating the identifier of a network slice supported by the session management function; and The information regarding the capabilities of the user equipment includes at least one of the following: information indicating the maximum number of data sessions supported by the user equipment; information indicating the data session attributes supported by the user equipment, and other information regarding the capabilities of the user equipment; information indicating that the user equipment supports Reflective Quality of Service (RQoS); information indicating that the user equipment supports multi-homed IPv6 PDU sessions; information indicating that the user equipment supports Access Service Bootstrapping, Handover, and Split (ATSSS) bootstrapping functionality and bootstrapping modes; information indicating that the user equipment supports the transmission of port management information containers; information indicating that the user equipment supports access performance measurement based on QoS flow rules; or information indicating that the user equipment supports secondary data network authentication and authorization on the Evolved Packet Core (EPC). The instructions, when executed by the at least one processor, further cause the first core network entity to: receive the information about the capabilities of the communication network from the user equipment; and The instructions, when executed by the at least one processor, also cause the first core network entity to: receive from the user equipment an identifier associated with the information about the capabilities of the user equipment, and use the identifier associated with the information about the capabilities of the user equipment to retrieve information capabilities of the user equipment.

5. The first core network entity according to any one of claims 3 to 4, wherein sending the instruction includes sending the instruction to the user equipment, and wherein the instruction, when executed by the at least one processor, further causes the first core network entity to perform: Receive a response from the user equipment to the sending of the instruction, the response indicating the success or failure of establishing or modifying the data session.

6. The first core network entity according to any one of claims 1 to 5, wherein the instructions, when executed by the at least one processor, further cause the first core network entity to: receive from the user equipment an indication that the service descriptor has ceased to be used by the user equipment; send an instruction to the user equipment, the instruction being configured to cause the user equipment to request the release of the data session; and receive from the user equipment a release completion message indicating that the data session has been released; When the instructions are executed by the at least one processor, the first core network entity also causes the user equipment to: receive from the user equipment an indication that the second service descriptor has ceased to be used by the user equipment; send to the user equipment an instruction configured to cause the user equipment to request the release of a second data session for the service described by the second service descriptor; and receive from the user equipment a release completion message indicating that the release of the second data session is complete.

7. A method for establishing a first core network entity of a communication network, the method comprising: Receive from the user equipment a service descriptor that has been initiated for use by the user equipment; Based on information about the capabilities of the user equipment and information obtained from entities in the communication network, a set of data session attributes for the service described by the service descriptor is determined; as well as The data session attribute set is provided to the second core network entity or the user equipment. The data session attribute set will be used to establish a data session for the service or to modify an existing data session for the service.

8. A user equipment, comprising: At least one processor; as well as At least one memory storing instructions, which, when executed by the at least one processor, cause the user equipment to perform: Sends a service descriptor that has begun to be used by the user equipment to the first core network entity of the communication network; The data session attribute set is received from the first core network entity. The data session attribute set will be used to establish a new data session for the service described by the service descriptor or to modify an existing data session for the service described by the service descriptor. as well as Initiate the establishment of the new data session or modify the existing data session that has the data session attribute set.

9. The user equipment of claim 8, wherein the initiation is based on receiving an instruction from the first core network entity or the second core network entity of the communication network, the instruction being configured to cause the user equipment to initiate the establishment of the data session based on the data session attribute set or to initiate the modification of the existing data session based on the data session attribute set.

10. The user equipment according to claim 8 or 9, wherein the instruction, when executed by the at least one processor, further causes the user equipment to: detect the successful establishment or modification of a data session; and send a response to the instruction to the first core network entity, the response indicating the successful establishment or modification of the data session; When the instruction is executed by the at least one processor, it also causes the user equipment to: detect a failure in the establishment or modification of the data session; and send a response to the instruction to the first core network entity, the response indicating a failure in the establishment or modification of the data session. The response indicating a failure to establish or modify the data session includes a reason value indicating the cause of the failure; When the instructions are executed by the at least one processor, the user equipment also causes the user equipment to: send information about the capabilities of the user equipment to the first core network entity for determining the data session attribute set, wherein the information about the capabilities of the communication equipment includes at least one of the following: information indicating the maximum number of data sessions supported by the user equipment; information indicating the data session attributes supported by the user equipment; and other information about the capabilities of the user equipment. Information indicating that the user equipment supports Reflection Quality of Service (RQoS); Information indicating that the user equipment supports multi-homed IPv6 PDU sessions; information indicating that the user equipment supports Access Service Bootstrapping, Switching and Splitting (ATSSS) bootstrapping function and bootstrapping mode; information indicating that the user equipment supports the transmission of port management information containers; information indicating that the user equipment supports access performance measurement according to QoS flow rules; or information indicating that the user equipment supports secondary data network authentication and authorization on the evolved packet core (EPC); When the instructions are executed by the at least one processor, the user equipment also causes the user equipment to: send an identifier associated with information about the capabilities of the communication network to the first core network entity, so that the first core network entity can retrieve the information about the capabilities of the communication network; When the instruction is executed by the at least one processor, it also causes the user equipment to: send the service descriptor to the first core network entity after the service descriptor ceases to be used by the user equipment; receive an instruction from the first core network entity, the instruction being configured to cause the user equipment to request the release of the data session; and release the data session. When the instruction is executed by the at least one processor, it also causes the user equipment to: after releasing the data session, send a release completion message to the first core network entity indicating that the data session has been released; When the instruction is executed by the at least one processor, it also causes the user equipment to: send an indication to the first core network entity that the second service descriptor has ceased to be used by the user equipment; and receive an instruction from the first core network entity, the instruction being configured to cause the user equipment to request the release of a second data session of the service described by the second service descriptor; and send a release completion message to the first core network entity indicating that the release of the second data session has been completed. When the instructions are executed by the at least one processor, the user equipment also performs the following actions: assigning a data session identifier (ID) to the data session; and providing the data session ID to the first core network entity.

Images