WO2025167965A1 - Communication method and apparatus - Google Patents

Abstract

The present application provides a communication method and apparatus, applicable to the field of communications. The method comprises: when an activated user of a terminal device is successfully authenticated, a second network element sends a first message to a first network element, wherein the first message comprises the identifier of the terminal device and the user identifier of the activated user, and the first message indicates that the activated user of the terminal device is successfully authenticated; on the basis of the first message, the first network element stores the user identifier of the activated user of the terminal device. In this way, the signaling overhead can be reduced when a protocol data unit session is established for the terminal device, the communication efficiency is improved, and reliable differentiated quality-of-service guarantee can be provided for a user.

Description

Communication method and device

This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on February 8, 2024, with application number 202410179371.4 and invention name “Communication Method and Device”, the entire contents of which are incorporated by reference into this application.

Technical Field

The embodiments of the present application relate to the field of communications, and more specifically, to a communication method and apparatus.

Background Art

Current mobile networks provide services to devices based on subscription information. With the development of the times, a user may own multiple different types of devices, and multiple users may share the same device at different times (for example, in shared terminal scenarios like car-sharing). This results in a break from a one-to-one relationship between service subscribers, device owners, and actual users.

Currently, when establishing a protocol data unit (PDU) session, a terminal device must report not only its own identity to the network, but also the user identity of the user currently using the terminal device, so that the network can manage the session based on the corresponding subscription information. This approach is not well-suited for shared terminal services and results in redundant signaling overhead.

Summary of the Invention

The present application provides a communication method and apparatus, in which, when the authentication of an activated user of a terminal device is successful, the network side can store the user identification of the activated user of the terminal device, so that when establishing a protocol data unit session for the terminal device, the dependence on information from the terminal device can be reduced, the signaling overhead can be reduced, the communication efficiency can be improved, and the user can be provided with reliable and differentiated service quality assurance.

In a first aspect, a communication method is provided. The method is performed by a first network element or a component (such as a chip or chip system) for the first network element, which is not specifically limited in this application. The method includes: receiving a first message indicating successful authentication of an activated user of a terminal device, the first message including a user identifier of the activated user; and storing the user identifier according to the first message.

Exemplarily, the first network element may include a unified data management network element or a mobility management network element.

In some possible implementations, storing the user identifier according to the first message may include: storing the user identifier in the context or contract information of the terminal device according to the first message.

In the present application, when the authentication of the activated user of the terminal device is successful, the first network element can store the user identification of the activated user of the terminal device, so that when establishing a protocol data unit session for the terminal device, the first network element can realize the network side's control over the session management based on the user identification of the activated user of the terminal device stored by it, which can reduce signaling overhead, improve communication efficiency, and provide users with reliable and differentiated service quality assurance.

In one embodiment, the first network element may include a unified data management network element.

In combination with the first aspect, in certain implementations of the first aspect, the method may further include: sending a first request message, the first request message may be used to request updating the contract information of the terminal device, and the first request message may include a user identifier and an identifier (ID) of the terminal device.

In some possible implementations, the method may further include: receiving a fourth message, where the fourth message may be used to indicate that the update of the contract information of the terminal device has been completed.

In one embodiment, the third network element may receive the first request message and update the subscription information of the terminal device stored therein according to the first request message. For example, the user identifier of the activated user may be added or updated in the subscription information of the terminal device.

In this application, by updating the contract information of the terminal device stored in the third network element, when establishing a protocol data unit session for the terminal device, the network side can control the session management based on the user's user identification, which can reduce signaling overhead, improve communication efficiency, and provide users with reliable and differentiated service quality guarantees.

In combination with the first aspect, in certain implementations of the first aspect, the method may further include: receiving a second message, which may be used to query the contract information of the terminal device; and sending a third message, which may include the contract information associated with the user identifier.

In combination with the first aspect, in some implementations of the first aspect, the third message may include the user identifier.

In one embodiment, the first network element may include a mobility management network element.

In combination with the first aspect, in certain implementations of the first aspect, the method may further include: receiving a second request message, the second request message being used to request establishment of a protocol data unit (PDU) session for a terminal device, and the second request message may include an identifier of the terminal device; determining, based on the identifier of the terminal device, a user identifier of an activated user of the terminal device; and sending a third request message, the third request message may be used to request creation of a session management context for the PDU session, and the third request message includes an identifier of the PDU session, an identifier of the terminal device, and a user identifier.

In a second aspect, a communication method is provided. The method is performed by a second network element or a component (such as a chip or chip system) for the second network element, which is not specifically limited in this application. The method includes: when authentication of an activated user of a terminal device is successful, sending a first message indicating successful authentication of the activated user of the terminal device, the first message including a user identifier of the activated user.

In a third aspect, a communication method is provided, which is performed by a third network element or a component (such as a chip or chip system) for the third network element, and is not specifically limited in this application. The method includes: receiving a first request message for requesting an update of contract information of a terminal device, the first request message including a user identifier of an activated user of the terminal device and an identifier of the terminal device; and updating the contract information of the terminal device stored in the third network element according to the first request message.

In one embodiment, updating the subscription information of the terminal device stored in the third network element may include adding or updating the user identifier of the activated user of the terminal device in the subscription information.

In combination with the third aspect, in certain implementations of the third aspect, the method may further include: sending a fourth message, where the fourth message may be used to indicate that the contract information of the terminal device has been updated.

In combination with the third aspect, in certain implementations of the third aspect, the subscription information may include session management control policy information.

In some possible implementations, the method may further include: receiving a fourth request message, the fourth request message may be used to request session management control policy information associated with the terminal device, and the fourth request message may include an identifier of the terminal device; determining the user identifier of the activated user of the terminal device based on the identifier of the terminal device; and sending a fifth message, the fifth message may include session management control policy information associated with the user identifier.

In some possible implementations, the method may further include: receiving a fifth request message, which may be used to request session management control policy information associated with the user identifier, and the fifth request message may include the user identifier; and sending a sixth message, which may include session management control policy information associated with the user identifier.

In a fourth aspect, a communication method is provided, which is performed by a session management function network element or a component (such as a chip or chip system) for the network element, and is not specifically limited in this application. The method includes: sending a second message, the second message being used to query the contract information of a terminal device, the second message including the identifier of the terminal device; and receiving a third message, the third message including the contract information associated with the user identifier of an activated user of the terminal device, the user identifier being determined based on the identifier of the terminal device.

In combination with the fourth aspect, in certain implementations of the fourth aspect, the method may further include: sending a sixth request message, the sixth request message may be used to request updating the session management control policy information for the PDU session of the terminal device, the sixth request message may include the identifier of the terminal device and the identifier of the PDU session; receiving a seventh message, the seventh message may include the session management control policy information associated with the user identifier.

In some possible implementations, the sixth request message may further include a user identifier of an activated user of the terminal device.

In a fifth aspect, a communication method is provided, which is performed by a policy control function network element or a component (such as a chip or chip system) used for the network element, and is not specifically limited in this application. The method includes: sending a fourth request message, the fourth request message being used to request session management control policy information associated with a terminal device, the fourth request message including an identifier of the terminal device; and receiving a fifth message, the fifth message including session management control policy information associated with a user identifier of an activated user of the terminal device.

In a sixth aspect, a device is provided, which may include a module or unit for implementing the method in any one of the first to fifth aspects and possible implementations thereof.

Illustratively, the apparatus includes a communication module.

In some possible implementations, the device may further include a processing module.

In some possible implementations, the device may further include a storage module.

In the seventh aspect, a device is provided, comprising at least one processor, the at least one processor being coupled to at least one memory, the at least one memory being used to store computer programs or instructions, and the at least one processor being used to call and run the computer program or instructions from the at least one memory, so that the device executes the method of any one of the first to fifth aspects, or the method of any possible implementation of the first to fifth aspects.

In one example, the apparatus of the seventh aspect may be a first network element, a second network element, a third network element, a policy control function network element, or a session management function network element.

In an eighth aspect, the present application provides a chip comprising a communication interface and a circuit, wherein the communication interface is used to receive information from other devices and input the information into the circuit, and/or the communication interface is used to send the information in the circuit to other devices, and the circuit is used to execute the method of any aspect from the first to the fifth aspect or any possible implementation thereof.

In a ninth aspect, the present application provides a computer-readable storage medium, in which computer instructions are stored. When the computer instructions are executed on a computer, the method in any one of the first to fifth aspects or any possible implementation thereof is implemented.

In a tenth aspect, the present application provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the method in any one of the first to fifth aspects or any possible implementation thereof is implemented.

In the eleventh aspect, the present application provides a communication system, including an apparatus as in any one of aspects 6 to 8, such as a first network element, a second network element, a third network element, a policy control function network element and/or a session management function network element.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of an application scenario applicable to an embodiment of the present application;

FIG2 is a schematic diagram of a process for establishing a protocol data unit session;

FIG3 is a schematic diagram of a business scenario provided in an embodiment of the present application;

FIG4 is a schematic diagram of a communication method provided in an embodiment of the present application;

FIG5 is a flow chart of another communication method provided in an embodiment of the present application;

FIG6 is a flow chart of another communication method provided in an embodiment of the present application;

FIG7 is a flow chart of another communication method provided in an embodiment of the present application;

FIG8 is a flow chart of another communication method provided in an embodiment of the present application;

FIG9 is a flow chart of another communication method provided in an embodiment of the present application;

FIG10 is a flow chart of another communication method provided in an embodiment of the present application;

FIG11 is a flow chart of another communication method provided in an embodiment of the present application;

FIG12 is a flow chart of another communication method provided in an embodiment of the present application;

FIG13 is a flow chart of another communication method provided in an embodiment of the present application;

FIG14 is a schematic diagram of a device provided in an embodiment of the present application;

FIG15 is a schematic diagram of another device provided in an embodiment of the present application;

FIG16 is a schematic diagram of a chip system provided in an embodiment of the present application.

DETAILED DESCRIPTION

The technical solution in this application will be described below with reference to the accompanying drawings.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as a long term evolution (LTE) system, a frequency division duplex (FDD) system, a time division duplex (TDD) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) communication system, a fifth generation (5G) system or a new radio (NR) system, a sixth generation (6G) system, or future communication systems. The 5G mobile communication system described in the present application includes a non-standalone (NSA) 5G mobile communication system or a standalone (SA) 5G mobile communication system. The communication system may also be a public land mobile network (PLMN), a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of things (IoT) communication system, a vehicle-to-everything (V2X) communication system, an uncrewed aerial vehicle (UAV) communication system, or other communication systems.

The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying drawings in the embodiments of the present application. In the description of the present application, unless otherwise specified, "/" indicates that the objects associated before and after are in an "or" relationship. For example, A/B can represent A or B. The "and/or" in the present application is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple. In addition, in order to facilitate a clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences. At the same time, in the embodiments of the present application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a concrete way for easy understanding.

In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

Figure 1 shows an application scenario to which the embodiments of the present application are applicable. As shown in Figure 1 , a network architecture 100 may include the following network elements.

1. User Equipment (UE): Also referred to as terminal equipment or terminal. Terminal equipment may include, but is not limited to, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal device, a mobile terminal device, a user terminal device, a wireless communication device, a user agent, a user device, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication capabilities, a computing device, a processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in the Internet of Things, a home appliance, a virtual reality device, a terminal device in a 5G network, or a terminal device in an evolved public land mobile network (PLMN), etc., and the embodiments of the present application are not limited thereto.

2. Radio access network (RAN): This is primarily responsible for air interface radio resource management, quality of service (QoS) management, data compression, and encryption. Access network equipment can include various base stations, such as macro base stations, micro base stations (also known as small stations), relay stations, and access points. In systems using different wireless access technologies, the names of devices with base station functions may vary. For example, in third-generation (3G) systems, they are called Node Bs; in LTE systems, they are called evolved Node Bs (eNBs or eNodeBs); and in 5G systems, they can be called gNBs.

3. Data network element: a digital transmission network used to transmit data communication services.

In a 5G communication system, a data network element can be a data network (DN) element. A DN refers to a carrier's network that provides data transmission services to users. Examples include the Internet Protocol (IP) Multimedia Service (IMS) and the Internet. A DN can be a carrier's external network or a carrier-controlled network used to provide services to terminals.

In future communication systems, the data network element may still be a DN element, or may have other names, which is not limited in this application.

4. Authentication, authorization, and accounting (AAA) server: responsible for authentication, authorization, and accounting.

In the 5G communication system, the AAA server can belong to the DN or the 5G core network.

5. Access management network element: mainly used for mobility management and access management, performing registration, connection, reachability and mobility management, responsible for providing session management message transmission channel between UE and session management network element, providing authentication and authorization functions for UE access, and is the access point of terminal and wireless core network control plane.

In a 5G communication system, the access management network element may be an access and mobility management function (AMF) network element. In future communication systems, the access management network element may still be an AMF network element, or may have other names, which are not limited in this application.

6. Session Management NE: This element is primarily responsible for session management and handles user services such as session establishment, modification, and release, as well as interaction with user plane functions. For example, its specific functions include allocating Internet Protocol (IP) addresses to users and selecting user plane function (UPF) elements that provide packet forwarding.

In a 5G communication system, a session management network element may be a session management function (SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or may have other names, which are not limited in this application.

7. Data management network element: performs contract management, access authorization, authentication information generation, etc. for users.

In a 5G communication system, the data management network element may be a unified data management (UDM) network element. In future communication systems, the data management network element may still be a UDM network element, or may have other names, which are not limited in this application.

8. User plane function network element: Mainly responsible for user data processing (forwarding, receiving, billing, etc.). For example, it can receive user data from the data network (DN) and forward the user data to the terminal through the access network equipment. The user plane function network element can also receive user data from the terminal through the access network equipment and forward the user data to the DN. In one embodiment, in a protocol data unit (PDU) session, the UPF directly connected to the DN through N6 is also called a protocol data unit session anchor (PSA).

9. Policy control network element: A unified policy framework used to guide network behavior and provide policy rule information for control plane functional network elements (such as AMF, SMF network elements, etc.).

In a 5G communication system, the policy control network element may be a policy control function (PCF) network element. In future communication systems, the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.

10. Network storage function network element: supports service discovery function, can receive NF discovery request from network function (NF) instance, and provide information of discovered NF instance to the NF instance.

In a 5G system, the network repository function network element may be a network repository function (NRF) network element. In future communication systems, the network repository function network element may still be an NRF network element, or may have other names, which are not limited in this application.

11. Authentication service function network element: provides authentication services.

In a 5G system, the authentication server function network element may be an authentication server function network element (AUSF). In future communication systems, the authentication server function network element may still be an NRF network element, or may have other names, which are not limited in this application.

For example, the representation of a 5G system architecture based on a reference point can be shown in Figure 1. N1, N2, N3, N4, and N6 are interface serial numbers. The meanings of these interface serial numbers can be found in related technologies, such as those defined in 3GPP TS 23.501. The service-oriented interfaces of network elements such as the AMF, SMF, UDM, and PCF can be denoted as Namf, Nsmf, Nudm, and Npcf, respectively, as shown in Figure 1.

The network architecture used in the embodiments of the present application is merely an example. The network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture capable of implementing the functions of the aforementioned network elements is applicable to the embodiments of the present application. In some possible implementations, the network architecture may include more or fewer network elements. For example, the network architecture may further include a network slice selection function (NSSF).

For example, the AMF, SMF, UPF, PCF, and UDM shown in Figure 1 can be understood as network elements used to implement different functions in the core network, and can be combined into network slices as needed. These core network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.

The above naming is only defined to facilitate the distinction between different functions and should not constitute any limitation to this application. This application does not exclude the possibility of adopting other naming in 5G networks and other networks in the future. For example, in a 6G network, some or all of the above networks may use the terminology in 5G, or other names may be used. The interface name between the various network elements in Figure 1 is only an example. The name of the interface in the specific implementation may be other names, and this application does not make specific limitations on this. In addition, the name of the message (or signaling) transmitted between the above-mentioned network elements is only an example and does not constitute any limitation on the function of the message itself.

For example, FIG2 is a schematic diagram of a process for establishing a PDU session. The method may include the following steps:

S201, the UE sends message #201 to request to establish a PDU session; accordingly, the AMF can receive message #201.

Message #201 may be referred to as a PDU session establishment request message, and may be denoted as PDU_Session_Establishment_Request.

Exemplarily, the PDU session establishment request message may include a PDU session identifier (PDU session identifier, PDU Session ID) and a request type (request type). The request type may include: initial request, existing PDU session, and emergency request. For example, when establishing a new PDU session, the request type may be initial request. For another example, when switching between 3GPP access and non-3GPP access for an existing PDU session, the request type may be existing PDU session. For another example, when establishing a PDU session for emergency services, the request type may be emergency request.

S202, AMF selects SMF.

Exemplarily, the AMF selects an SMF to manage the PDU session for the PDU session. For example, the AMF may select an SMF based on pre-configured available SMFs. For another example, the AMF may select an SMF for the PDU session based on network slice selection assistance information (NSSAI) received during configuration or during the UE registration process. NSSAI is a set of single NSSAI (S-NSSAI), which may include configured NSSAI, requested NSSAI, and/or allowed NSSAI.

In some possible implementations, when the S-NSSAI is not carried in the non-access-stratum (NAS) message, the AMF may determine the network slice information of the serving PLMN of the requested PDU session from the NSSAI currently allowed by the UE.

In one embodiment, when the allowed NSSAI only includes network slice information of one serving PLMN, the network slice information is adopted.

In another embodiment, when multiple network slice information is included in the allowed NSSAI, the network slice selection auxiliary information can be selected based on the UE's subscription information or the network slice information can be determined based on the operator policy. For example, when the UE's subscription information only includes a default S-NSSAI and the corresponding serving PLMN's mapped home PLMN (HPLMN) is included in the allowed NSSAI, the network slice information of the serving PLMN of the requested PDU session can be determined based on the UE's subscription information. For another example, the operator policy can support a selected S-NSSAI to allow any UE-requested data network name (DNN) to be used as the S-NSSAI. In this scenario, the network slice information can be determined based on the operator policy.

In some possible implementations, when the NAS message contains the network slice information of the serving PLMN but does not contain the DNN, and the UE's subscription information includes a default DNN, the AMF may use the DNN corresponding to the slice information in the subscription information as the DNN for the requested PDU session. If the UE's subscription information does not include a default DNN, the AMF may select a locally configured DNN for the S-NSSAI of the serving PLMN.

For example, the AMF may discover a suitable SMF based on the network selection auxiliary slice information and the network data name. When the request type is an initial request, the AMF may store the relationship between the slice S-NSSAI, DNN, PDU session identifier, SMF ID, and access type of the PDU session.

S203, AMF sends message #203; accordingly, SMF receives message #203.

The AMF sends a message #203 to the selected SMF to request the SMF to establish a PDU session. Message #203 can be used to request the creation of a session management context for the PDU session, which can be recorded as Nsmf_PDUSession_CreateSMContext_request.

Exemplarily, message #203 may include: the selected DNN, the subscription permanent identifier (SUPI) of the UE requesting to establish a PDU session, the DNN requested by the UE, and network slice selection auxiliary information.

Optionally, in S204, the SMF queries the UDM for the subscription information of the UE.

For example, when the session management subscription data of the HPLMN corresponding to SUPI, DNN, and S-NSSAI is not available, the SMF may query the UDM for the UE's subscription information. When the session management subscription data of the HPLMN is available, step S204 may be skipped.

S205, SMF sends message #205; accordingly, AMF receives message #205.

Message #205 may be a response message to message #203, and may be recorded as Nsmf_PDUSession_CreateSMContext_response.

In one embodiment, when accepting the establishment request of the PDU session, the SMF may create a session management (SM) context for the session; accordingly, message #205 may include an identifier of the session management context.

In another embodiment, when the SMF does not accept the request to establish a PDU session, message #205 may include the reason for refusing to establish the PDU session.

S206: PDU session authentication/authorization.

In one embodiment, when the request type is an initial request, step S206 may be executed to authenticate the PDU session.

In another embodiment, when the request type is an existing PDU session or an emergency request, step S206 may be skipped.

In another embodiment, based on the session management policy associated with the DN, the SMF can determine whether secondary authentication is required for the PDU.

Optionally, in S207 , the SMF selects the PCF.

In one embodiment, when a PDU session adopts dynamic policy and charging control (PCC) rules, step S207 is executed to select an appropriate PCF for the PDU session.

In another embodiment, when the PDU session does not adopt the dynamic PCC rule, step S207 may be skipped.

S208: Associating a session management policy with the PDU session.

For example, the SMF may send a message to the PCF requesting association of a session management policy. The message may include the UE's SUPI. Based on the SUPI, the PCF may determine the session management policy associated with the SUPI. The PCF may send a response message to the SMF. The response message may include session management policy information for the PDU session.

S209, select UPF.

The SMF may select a UPF for the PDU session. For example, the SMF may select a UPF based on information about available UPFs configured locally. For another example, the SMF may select a UPF for the PDU session based on the location of the UPF, the location of the UE, and/or the dynamic load of the UPF.

The SMF may also allocate an IP address for the PDU session.

In one embodiment, when the request type is an initial request, the SMF may also allocate a session and service continuity mode (SSC) for the PDU session.

S210, SMF sends message #210; accordingly, AMF can receive message #210.

Message #210 may include relevant information of the PDU session, such as information of the N3 tunnel associated with the PDU session, uplink and downlink rate information, UE IP information, etc.

The PDU session related information contained in message #210 can be forwarded to the UE via the N1 and/or N2 tunnels. This message #210 can be recorded as Namf_Communication_N1N2MessageTransfer.

S211, AMF sends message #211; accordingly, RAN can receive message #211.

In one embodiment, the AMF may send relevant information of the PDU session to the UE via an N2 message.

Message #211 may include relevant information about the PDU session and may be recorded as N2_PDU_Session_request. Message #211 may be a NAS message.

S212, RAN sends message #212; correspondingly, UE receives message #212.

Message #212 may include relevant information about the PDU session and may be used to indicate that the network has accepted the establishment of the PDU session. Message #212 may be recorded as PDU_Session_Establishment_Accept.

Exemplarily, through steps S210 to S212, the SMF may send relevant information of the PDU session to the UE.

In a traditional solution (using method 200 as an example), the mobile network provides services to the UE based on subscription information. For example, the core network provides network services to the user based on the UE's subscriber identification module (SIM). The user subscribes to network services using the SIM card. When the user requests a certain network service, the core network identifies the SIM card's identifier (e.g., SUPI), determines the subscription information for the SUPI, and provides the corresponding network service. In this approach, the user and the SIM card are strongly bound.

For services like voice and short message service (SMS), a user has only one terminal device. Accordingly, providing a single set of subscription data for that terminal device is sufficient to meet their needs. However, with the changing times, a user may own different types of terminal devices (such as mobile phones, tablets, and laptops), and the same terminal may be shared by different users. Traditionally, different users who need to access different services through the same terminal must replace the SIM card in the UE, which degrades the user experience.

To reduce the strong binding between users and SIM cards, user identifiers (IDs) can be used to distinguish different users. A user ID represents the person logged into a UE at a given moment. Only one user can be logged into a UE at a time. The core network can provide services based on the subscription information for each user account. Operators can make user ID information available to third parties, allowing users to use it to register or log into third-party applications.

For example, FIG3 is a schematic diagram of a business scenario provided by an embodiment of the present application.

A mobile network operator (MNO) can provide a variety of network services. The owner of a shared terminal (such as the vehicle in Figure 3) (e.g., a car rental company) can purchase a contract for the terminal to access the network from the MNO. Users can purchase contracts for network services from the MNO. After the terminal registers and accesses the network based on the contract information for accessing the network, different users can log in to the terminal using their own user IDs. The core network can provide different services to users through the vehicle based on the contract information for the network services purchased by the users. For example, as shown in Figure 3, when user A uses the shared vehicle, the core network can provide user service #1 based on the network services purchased by user A. For another example, as shown in Figure 3, when user B uses the shared vehicle, the core network can provide user service #2. In other words, on the same terminal, different users can enjoy different levels and categories of services through different user IDs.

In the scenario shown in Figure 3, the UE needs to carry a user ID in the message it sends to the network to identify the user using the UE, thereby obtaining the required user files to achieve differentiated quality of service (QoS). That is, each time a PDU session is established, the PDU session establishment request message needs to carry the user ID; accordingly, the multiple messages involved in the PDU session establishment process also need to include the user ID. For example, message #201, message #203, the message involved in step S204, the message involved in step S208, and messages #210 through #212 need to include the user ID. This approach is not suitable for this usage scenario and results in signaling redundancy.

In view of this, an embodiment of the present application provides a communication method and device, which enables the network to know whether a user has logged into the UE and the identification of the user logged into the UE in a more efficient manner, and can accurately provide differentiated QoS guarantees.

For example, Figure 4 is a schematic diagram of a communication method provided by an embodiment of the present application. For the sake of convenience of description, the following is an illustrative explanation using the execution subjects of the method shown in Figure 4 as the first network element, the second network element, the third network element, the terminal device, the RAN, the SMF and the PCF. It can be understood that the execution subject of the method shown in Figure 4 can also be a component of the above-mentioned network elements or devices, such as a chip or a chip system or a circuit, and the embodiment of the present application does not limit this. The steps described below as being performed by a single execution subject can also be divided into being performed by multiple execution subjects, and these execution subjects can be logically and/or physically separated. The method 400 may include the following steps:

S401: The second network element authenticates the activated user of the UE.

Exemplarily, the second network element may provide an authentication service. The authentication may be a primary authentication or a secondary authentication. For example, when the authentication process occurs during the UE's registration process, the authentication may be a primary authentication.

In one embodiment, the second network element may include an AUSF.

In another embodiment, the second network element may include an AMF.

In another embodiment, the second network element may include an AAA server. For example, the AAA server may provide a secondary authentication service.

In some possible implementations, the second network element may also be other network elements that can provide authentication services, which is not limited in the embodiments of the present application.

S402, the second network element sends a first message; correspondingly, the first network element receives the first message.

When the authentication of the active user of the UE is successful, the second network element may send a first message to the first network element. The first message may include a user identifier of the active user of the UE. The first message may indicate the successful authentication of the UE and the user.

Exemplarily, the active user of a UE may also have other names, such as the user currently using the UE, the currently logged-in user of the UE, or the currently active user of the UE. For example, if user #1 is the active user of the UE, when the user ID of user #1 is successfully authenticated, the first message may include the user ID of user #1.

In one embodiment, the first network element may include an AMF.

In another embodiment, the first network element may include a UDM.

S403: The first network element stores the user identifier of the activated user of the UE according to the first message.

Exemplarily, the first network element may be configured to store data of the UE, or in other words, the first network element may store data of the UE. The UE data may include, for example, UE context information, UE subscription information, etc. Based on the first message, the first network element may add and/or update the user ID of the activated user in the stored data of the UE.

In one embodiment, the first network element may add and/or update the user ID of the activated user of the UE in the context information of the UE stored therein.

In another embodiment, the first network element may add and/or update the user ID of the activated user of the UE in the subscription information of the UE stored therein.

In some possible implementations, the first network element may add and/or update the user ID of the activated user of the UE in other data of the UE stored therein. The embodiment of the present application does not limit the data structure used to store the user ID.

In an embodiment of the present application, when authentication of the active user of the UE is successful, the network element responsible for authentication may indicate the authentication result to the first network element. Accordingly, the first network element may store the user ID of the user, thereby storing the identity of the active user of the UE on the network side. Thus, during the PDU session establishment process, relevant information (e.g., session management control policy information, subscription information, etc.) can be obtained based on the user ID of the active user of the UE stored by the first network element, thereby reducing signaling overhead.

In some possible implementations, other network elements in the network architecture may also be used to store UE-related information. For example, a third network element may be used to store UE subscription information.

Optionally, the method 400 may further include one or more of steps S404 to S406.

S404, the first network element sends a first request message; correspondingly, the third network element receives the message.

Exemplarily, the third network element may be used to store relevant data of the UE, such as subscription information of the UE. For example, the third network element may include a UDR.

The first request message may include a user identifier of an activated user of the UE. The first request message may be used to request updating of subscription information of the UE.

S405: The third network element updates the stored data of the UE according to the first request message.

Illustratively, based on the first request message, the third network element may update relevant data of the UE. For example, the third network element may add or update the user identifier of the activated user of the UE in the stored UE data. For example, the UE data may be the UE's subscription information. The specific type of this data is not limited in this embodiment of the present application.

In an embodiment of the present application, since the third network element has updated the stored UE data, in the process of establishing the PDU session, it can provide relevant information about the PDU session based on the stored UE related data, and can provide users with more reliable QoS service guarantees.

S406, the first network element sends indication information to indicate the authentication result; correspondingly, the UE receives the indication information.

The indication information may indicate that the authentication is successful.

As described above, since the first network element and the third network element can store the user ID of the activated user of the UE, during the establishment of the PDU session, relevant information can be provided based on the stored user ID of the activated user of the UE.

In some possible implementations, the first network element may store subscription information of different UEs and/or subscription information of different users. For example, the first network element may be a UDM.

Exemplarily, the SMF may send a second message to the first network element. The second message may be used to query the subscription information of the UE and may include the identifier of the UE. The first network element may determine the user ID of the active user of the UE based on the identifier of the UE; and may determine the subscription information associated with the user ID based on the user ID of the active user of the UE. The first network element may send a third message to the SMF. The third message may include the subscription information associated with the user ID.

In one embodiment, the third message may also include the user ID.

In some possible implementations, the SMF can determine whether to perform secondary authentication based on the contract information associated with the user ID.

In some possible implementations, the first network element may not store relevant data such as the UE's subscription information. During the UE PDU session establishment process, the first network element may determine the user ID of the UE's active user from its stored data based on the UE identifier, so that the PDU session can be associated with the user ID of the user.

Exemplarily, the first network element may receive a second request message, where the second request message may be used to request creation of a PDU session for the UE, and the second request message may include an identifier of the UE. The first network element may determine, based on the identifier of the UE, a user ID of an active user of the UE. The first network element may send a third request message to the SMF, where the third request message may be used to create a session management context for the PDU session. The third request message may include an identifier of the PDU session, an identifier of the UE, and an user ID of an active user of the UE.

In some possible implementations, the third network element may be used to store the subscription information. For example, the third network element is a UDR.

In one embodiment, after the third network element completes the update of the subscription data of the UE, it may send a fourth message to the first network element, and the fourth message may be used to indicate that the subscription information of the UE has been updated.

In some possible implementations, the subscription information stored by the third network element may include session management control policy information. During the establishment process of the UE's PDU session, the third network element may provide the stored session management control policy information to other network elements.

Exemplarily, the SMF may send a request message (e.g., the sixth request message) to the PCF to request an update of session management control policy information for the PDU session of the UE. The PCF may send a message (e.g., the seventh message) to the SMF, which may include session management control policy information associated with the user ID of the active user of the UE. For example, if the PCF does not store the session management control policy information associated with the user ID, the PCF may obtain the session management control policy information from a third network element.

In one embodiment, the PCF may send a fourth request message to a third network element. The fourth request message may be used to request session management control policy information associated with the UE, and the message may include an identifier of the UE. The third network element may determine the user ID of the active user of the UE based on the identifier of the UE, and determine the session management control policy information associated with the user ID. The third network element may send a fifth message to the PCF, which may include the session management control policy information associated with the user ID.

In another embodiment, the PCF may send a fifth request message to the third network element. The fifth request message may include a user ID and may be used to request session management control policy information associated with the user ID. The third network element may send a sixth message to the PCF. The sixth message may include the session management control policy information associated with the user ID.

In this embodiment of the present application, upon successful authentication of the UE's active user, the network may store the user ID of the UE's active user. When establishing the UE's PDU, relevant information may be queried based on the stored user ID of the UE's active user, thereby providing reliable QoS service guarantees for the user.

For example, the following, in combination with Figures 5 to 7, takes AUSF as the second network element as an example to briefly introduce the main authentication process performed by AUSF. The main authentication may include a two-way authentication process between the UE and the network. The main authentication may occur during the registration process of the UE, for example, when the UE first accesses the network or initiates a service request. Among them, Figure 5 shows the registration process of the UE; Figures 6 and 7 show the main authentication process performed by AUSF.

Figure 5 is a schematic diagram of another communication method provided by an embodiment of the present application. Figure 5 shows the registration process of a UE.

As shown in FIG5 , the method 500 may include the following steps:

S501: UE sends a registration request message.

The registration request message may include the UE identifier and the registration type.

Exemplarily, registration types may include initial registration, mobility registration update, periodic registration update, and emergency registration.

In one embodiment, when the UE is in a deregistered state, the registration type of the registration process initiated may be an initial registration. For example, the deregistered state may include a CM-IDLE state, in which there is no connection between the UE and the RAN, and between the RAN and the 5GC.

In another embodiment, when the UE needs to re-initiate a registration process due to mobility, the registration type of the initiated registration process may be mobility registration update. For example, the UE may be in the RM-registered state, and the UE's location may be updated through the mobility registration update.

In another embodiment, when the periodic registration update timer of the UE times out, the registration type of the registration process initiated may be periodic registration update. At this time, the UE may be in the registered RM-registered state.

In another embodiment, when the UE is in a service-restricted state, the registration type of the initiated registration process may be emergency registration.

Exemplarily, the UE identifier may include a subscription concealed identifier (SUCI), a 5G globally unique temporary UE identity (5G-GUTI) or a permanent equipment identifier (PEI).

In one embodiment, when the UE has a valid 5G-GUTI, the registration request message may include the 5G-GUTI.

In another embodiment, when the UE does not have a valid 5G-GUTI, the registration request message may include SUCI.

In another embodiment, in emergency registration, when the UE does not have a valid 5G-GUTI and does not have a SUCI or SUPI, the registration request message may include a PEI.

In some possible implementations, the UE identifier used in the registration request message may also be other identifiers, which is not limited in the embodiments of the present application.

S502: RAN selects a suitable AMF.

S503: The RAN sends a registration request message of the UE to the selected AMF.

S504: AMF selects a suitable AUSF for authentication.

S505: UE, AMF, AUSF and UDM interact to perform authentication.

In one embodiment, the extensible authentication protocol (EAP)-authentication and key agreement (AKA) mechanism can be used for authentication.

In another embodiment, EAP-enhanced authentication and key agreement (AKA’) mechanism can be used for authentication.

Exemplarily, the UE may be authenticated according to the UE's identifier (such as SUPI).

For example, when authenticating the user currently using the UE, the registration request message in step S501 and the registration request message in step S503 may also include the user identifier of the user. The user may be authenticated based on the user identifier. In this case, step S505 may correspond to step S401.

S506: AMF can interact with UDM to obtain the UE's subscription data.

After the UE and the network have successfully authenticated each other, the AMF can interact with the UDM through the UE's identity to obtain the UE's subscription data.

In some possible implementations, after successful authentication of the user, the AMF may obtain the user's subscription data from the UDM.

S507, AMF sends message #507; accordingly, RAN receives message #507.

The message #507 may include an N2 message. The N2 message may include information that the RAN needs to forward to the UE, such as registration acceptance information. The registration acceptance information may indicate that the network has accepted the UE's registration request.

S508, RAN sends message #508; correspondingly, UE receives the message #508.

The message #508 may include a NAS message and may include registration reception information.

For example, the following briefly describes the primary authentication process performed by the AUSF using Figures 6 and 7 as the second network element. The security anchor function (SEAF) network element mentioned in Figures 6 and 7 can be used to generate security root keys for the access layer and non-access layer. The SAEF is set in the AMF and can be deployed together with the AMF, rather than existing as an independent network function in the system architecture.

FIG6 is a flow chart of another communication method provided by an embodiment of the present application. Method 600 may include the following steps:

S601, UE sends message #601; correspondingly, SEAF receives the message #601.

Message #601 may include the UE's identifier, such as SUCI or 5G-GUTI.

S602, SEAF sends message #602; accordingly, AUSF receives the message #602.

Message #602 may be used to request authentication for the UE and may be recorded as Nausf_UEAuthentication_Authenticate_Request.

Exemplarily, message #602 may include SUPI or SUCI, and may also include the name of the serving network (SNN).

In one embodiment, when the message received by SEAF carries 5G-GUTI, SUPI is carried when the UE is authenticated again.

The SNN can be constructed by the UE or SEAF, and the AUSF can receive the SNN constructed by the SEAF.

For example, when the AUSF receives message #602, by comparing the service network name carried in message #602 with the name of the expected service network, it can determine whether the SEAF that sent the message is authorized to use the service network name carried in the message. The name of the service network can be used to derive the anchor key. On the one hand, the name of the service network can bind the anchor key to the service network by including the identifier of the service network. On the other hand, the name of the service network can include a service code set to "5G" to ensure that the anchor key is dedicated to the authentication between the 5G core network and the UE.

S603, AUSF sends message #603; accordingly, UDM/APRF/SIDE receives the message #603.

Message #603 can be used to query the UE's authentication information and can be recorded as Nudm_UEAuthentication_Get_Request.

Message #603 may include SUPI/SUCI, and SNN.

In one embodiment, after receiving message #603, when message #603 includes SUCI, the UDM may call a subscriber identity discovery function (SIDF) network element to determine the SUPI corresponding to the SUCI.

S604: Select an authentication method based on the SUPI.

UDM/ARPF can select the authentication method based on SUPI.

Exemplarily, when it comes to authentication of the user currently using the UE, message #601 and message #602 may also include the user identification of the user.

For example, the following takes the authentication method EPA-AKA’ as an example and introduces the main authentication process performed by AUSF in combination with Figure 7.

FIG7 is a flow chart of another communication method provided by an embodiment of the present application. Method 700 may include the following steps:

S701, UDM generates an authentication vector (AV).

The UDM can select an authentication method based on the contract information and generate an authentication vector. The authentication vector can include an expected response (ERES) and an authentication token (AUTN).

S702, UDM sends message #702; accordingly, AUSF receives message #702.

Message #702 may include the authentication vector. Message #702 may include a response message to message #603, which may be recorded as Nudm_UEAuthentication_Get_Response.

In some possible implementations, message #702 may also include one or more of SUPI, authentication and key management for applications (AKMA) indication, and routing indication.

S703, AUSF sends message #703; accordingly, SEAF receives the message #703.

Message #703 may be recorded as Nausf_UEAuthentication_Authenticate_Response.

Message #703 may include authentication information, such as AUTN.

S704, SEAF sends message #704; correspondingly, UE receives the message #704.

SEAF may transparently transmit the authentication information to the UE. Message #704 may include an authentication request message from the core network to the UE, which may be recorded as Auth-Req.

S705: Determine the authentication response.

The UE can authenticate the core network based on the AUTN.

S706, UE sends message #706; correspondingly, SEAF receives the message.

After the identity authentication is passed, the UE can send an authentication response message to the core network.

Message #706 may include an authentication response message, which may be denoted as Auth-Resp.

S707, SEAF sends message #707; accordingly, AUSF receives the message.

Message #707 can be recorded as Nausf_UEAuthentication_Authenticate_Request.

S708: Verify the authentication response.

Through steps S706 and S707, AUSF can obtain the authentication response of the UE.

The AUSF can compare the UE's authentication response with the authentication vector sent by the UDM. If the two are consistent, the serving network authentication is successful.

Optionally, in S709 , EAP messages are exchanged.

The AUSF and UE can exchange more EAP messages through SEAF, such as EAP request/AKA’ notification message and EAP response/AKA’ notification message.

S710, AUSF sends message #710; accordingly, SEAF receives the message.

Message #710 can be recorded as Nausf_UEAuthentication_Authenticate_Response.

Message #710 may include EAP success information, anchor key, and SUPI. The EAP success information may indicate that the authentication is successful.

S711, SEAF sends message #711; correspondingly, UE receives the message.

Message #711 may include EAP success information.

Through steps S710 and S711 , the UE can obtain the authentication result.

Exemplarily, steps S601 to S604 , and steps S701 to S711 may correspond to step S505 .

Exemplarily, the following takes AUSF as the second network element, UDM as the first network element, and UDR as the third network element as an example, and briefly introduces the method 400 in conjunction with Figure 8. Figure 8 shows a registration process of a UE.

FIG8 is a flow chart of another communication method provided by an embodiment of the present application. Method 800 may include:

S801, UE sends message #801; accordingly, RAN receives the message.

Message #801 may include the UE identifier (such as SUCI or 5G-GUTI) and the user ID of the user currently using the UE.

S802: RAN selects a suitable AMF.

S803, RAN sends message #803; accordingly, AMF receives the message.

Message #803 may include the UE identifier (such as SUCI or 5G-GUTI) and the user ID of the user currently using the UE.

S804, AMF selects a suitable AUSF.

Exemplarily, steps S801 to S804 may correspond to steps S501 to S504. Accordingly, message #801 may be a registration request message.

S805, AMF sends message #805; accordingly, AUSF receives the message.

Message #805 may include SUCI and the user ID of the user currently using the UE.

S806, AUSF sends message #806; accordingly, UDM receives the message.

Message #806 may include SUCI and the user ID of the user currently using the UE.

In one embodiment, steps S805 and S806 may correspond to steps S602 and S603. Accordingly, message #805 may be Nausf_UEAuthentication_Authenticate_Request; and message #806 may be Nudm_UEAuthentication_Get_Request.

S807: UDM selects an authentication method and generates an authentication vector.

For example, the UDM can select an authentication method based on the user ID of the user currently using the UE and generate an authentication vector.

S808, UDM sends message #808; accordingly, AUSF receives the message.

Message #808 may include SUPI and authentication vector.

Step S808 may correspond to step S702. Accordingly, message #808 may be a response message to message #806, and may correspond to message #702, and may be recorded as Nudm_UEAuthentication_Get_Response.

S809: UE, RAN, AMF and AUSF interact to perform authentication.

Through step S809, the user currently using the UE can be authenticated.

In one embodiment, step S809 may correspond to steps S703 to S708.

In another embodiment, steps S801 to S809 may correspond to step S401.

S810, AUSF sends message #810; accordingly, UDM receives the message.

When the authentication is successful, the AUSF may send a message #810 to the UDM. Message #810 may include the UE's identifier (e.g., SUPI), the user ID of the user currently using the UE, and an indication that the authentication was successful.

Message #810 can be recorded as Nudm_UserAuthentication_ResultConfimation_Request.

In one embodiment, step S810 may correspond to step S402, and message #810 may be an example of a first message.

S811, the UDM adds/updates information in the stored data of the UE to indicate the user currently using the UE.

Exemplarily, the UE data stored by the UDM may include UE context information. Based on the UE's identifier, the UDM may retrieve the UE's context from its stored UE contexts and add information to the UE's context to indicate the user currently using the UE. For example, assuming the user identifier is user ID#1, the text "active user: user ID#1" may be added to the UE's context information to indicate the user currently using the UE.

In one embodiment, step S811 may correspond to step S403.

S812: The UDM interacts with the UDR to associate or update the session management policy.

In some possible implementations, the UDR may store relevant data of different UEs and may also store relevant data of different users.

Exemplarily, the UDM may send a data update request message to the UDR to request updating of data stored in the UDR. The message may be recorded as Nudr_DM_Update.

In one embodiment, the data update request message may include the UE identifier (such as SUPI) and the user ID currently using the UE. After receiving the message, the UDR may add information to the UE-related data stored in it to indicate the user currently using the UE.

Step S812 may correspond to step S404, and the data update request message may be taken as an example of a first request message.

In some possible implementations, after completing the update of the relevant data of the UE, the UDR may send a response message to the UDM to indicate that the data update has been completed. The response message may be used as an example of the fourth message.

S813, UDM sends message #813; accordingly, AUSF receives the message.

Message #813 may be recorded as Nudm_UserAuthentication_ResultConfimation_Response, which may be a response message to message #810.

S814, AUSF sends message #814; accordingly, AMF receives the message.

Message #814 may be a response message to message #805 and may include an authentication result.

S815, AMF sends message #815; accordingly, UE receives the message.

Message #815 may include the user ID currently using the UE.

In one embodiment, steps S814 and S815 may correspond to step S406.

In yet another embodiment, steps S814 and S815 may correspond to steps S710 and S711, respectively.

In an embodiment of the present application, the UDM can store the identifier of the user currently using the UE. In this way, the UDM can query relevant information about the user, such as subscription information and policy information related to the PDU session, based on the stored user identifier. During the PDU session establishment process, signaling overhead can be reduced and communication efficiency can be improved.

For example, the following still takes UDM as the first network element, AUSF as the second network element and UDR as the third network element as an example, and describes the process of establishing a PDU session in combination with Figure 9.

FIG9 is a flow chart of another communication method provided by an embodiment of the present application. Method 900 may include:

S901, UE sends message #901; accordingly, AMF receives the message.

Message #901 may be used to request the establishment of a PDU session and may include an identifier of the PDU session.

S902, AMF selects SMF.

S903, AMF sends message #903; accordingly, SMF receives the message.

Message #903 may include the identifier and SUPI of the PDU session.

In one embodiment, steps S901 to S903 may correspond to steps S201 to S203.

S904, SMF sends message #904; accordingly, UDM receives the message.

Message #904 may include SUPI. Message #904 may be used to query the subscription data of the user currently using the UE, and may be recorded as Nudm_SDM_Get.

In one embodiment, message #904 may be used as an example of the second message.

S905: The UDM confirms the user file of the user currently using the UE based on the stored data of the UE.

Exemplarily, the UE data stored by the UDM may include the UE's context. Assume that the UDM has added and/or updated the user ID of the active user of the UE in the UE's context according to method 800.

In one embodiment, the UDM can find the UE context corresponding to the SUPI from among the multiple UE contexts it stores. Based on the user ID of the user currently using the UE carried in the UE context, the UDM can determine the subscription data corresponding to the user ID, such as user level, IP address, QoS parameters, etc.

S906, UDM sends message #906; correspondingly, SMF receives the message.

Message #906 may include a user file of the user currently using the UE, and the user file may include subscription data of the user.

In some possible implementations, message #906 may also include the user’s user ID.

In one embodiment, message #906 may be used as an example of the third message.

S907, SMF sends message #907; accordingly, AMF receives the message.

The SMF can determine whether to allow the establishment of a PDU session based on the user's subscription data. When the establishment of a PDU session is allowed, the SMF can create a session management context for the PDU session.

Message #907 may include an identifier of the session management context of the PDU session.

In some possible implementations, S908 , the PDU session is authenticated.

The SMF may determine whether a secondary authentication is required for the PDU session based on the user's subscription data and/or the session management policy associated with the DN. For example, when the user's subscription data includes an indication for secondary authentication of the PDU session, the SMF performs secondary authentication on the PDU session.

S909: The SMF selects a suitable PCF.

S910, SMF sends message #910; correspondingly, PCF receives the message.

Message #910 may include the SUPI and the identifier of the PDU session. Message #910 may be used to request an update of the session management control policy and may be recorded as Npcf_SMPolicyControl_Update_Request.

In some possible implementations, message #910 may also include a user ID.

In one embodiment, message #910 may be used as an example of the sixth request message.

S911, PCF sends message #911; accordingly, UDR receives the message.

If the PCF does not store subscription data associated with the user ID of the user currently using the UE, the PCF may send a message to the UDR to query the subscription data associated with the user ID. Message #911 may be recorded as Nudr_DM_Query_Request.

In one embodiment, message #911 may include the SUPI. Accordingly, the UDR may query the relevant data of the UE based on the SUPI and obtain the user ID of the user currently using the UE from the relevant data. The UDR may also query relevant data associated with the user ID and send it to the PCF. In this scenario, message #911 may serve as an example of the fourth request message; the response message to message #911 may serve as an example of the fifth message.

In another embodiment, message #911 may include the user ID of the user currently using the UE. Accordingly, the UDR may query data related to the user based on the user ID. In this scenario, message #911 may serve as an example of the fifth request message; the response message to message #911 may serve as an example of the sixth message.

Exemplarily, when a session management policy related to a user currently using the UE is stored in the PCF, steps S911 and S912 may be skipped.

S912, UDR sends message #912; correspondingly, PCF receives the message.

The UDR can query the stored data related to the UE and the data related to the user currently using the UE.

Message #912 may include session management control policy information of the PDU session, such as user level, maximum aggregate bit rate of QoS flow corresponding to DNN/S-NSSAI, allowed services, etc.

Message #912 may include a response message to message #911.

S913, PCF determines to update the policy associated with the PDU session, or determines to send a new policy to SMF.

S914, PCF sends message #914; correspondingly, SMF receives the message.

Message #914 may include session control policy information for the PDU session corresponding to the user ID of the user.

Message #914 may include a response message to message #910, which may be recorded as Npcf_SMPolicyControl_Update_Response.

In one embodiment, message #914 may be used as an example of the seventh message.

S915, SMF selects the appropriate UPF.

S916: Establish a PDU session.

Exemplarily, steps S915 and S916 may correspond to steps S209 to S212 .

Exemplarily, the following takes AUSF as the second network element and AMF as the first network element as an example, and briefly introduces the method 400 in conjunction with Figure 10. Figure 10 shows a registration process of a UE.

FIG10 is a flow chart of another communication method provided by an embodiment of the present application. The method 1000 may include the following steps:

S1001, UE sends message #1001; accordingly, RAN receives the message.

Message #1001 may include the UE identifier (such as SUCI or 5G-GUTI) and the user ID of the user currently using the UE.

S1002: RAN selects a suitable AMF.

S1003, RAN sends message #1003; accordingly, AMF receives the message.

Message #1003 may include the UE identifier (such as SUCI or 5G-GUTI) and the user ID of the user currently using the UE.

S1004, AMF selects a suitable AUSF.

S1005, AMF sends message #1005; accordingly, AUSF receives the message.

Message #1005 may include SUCI and the user ID of the user currently using the UE.

S1006, AUSF sends message #1006; accordingly, UDM receives the message.

Message #1006 may include SUCI and the user ID of the user currently using the UE.

S1007: UDM selects an authentication method and generates an authentication vector.

For example, the UDM can select an authentication method based on the user ID of the user currently using the UE and generate an authentication vector.

S1008, UDM sends message #1008; accordingly, AUSF receives the message.

Message #1008 may include SUPI and authentication vector.

Step S1008 may correspond to step S702. Accordingly, message #1008 may be a response message to message #1006, and may correspond to message #702, and may be recorded as Nudm_UEAuthentication_Get_Response.

S1009: UE, RAN, AMF and AUSF interact to perform authentication.

Exemplarily, steps S1001 to S1009 may correspond to steps S801 to S809.

S1010, AUSF sends message #1010; accordingly, AMF receives the message.

Upon successful authentication, the AUSF may send message #1010 to the AMF. Message #1010 may include the UE's identifier (e.g., SUPI), the user ID of the user currently using the UE, and an indication that the authentication was successful.

Message #1010 may be recorded as Nausf_UserAuthentication_Authenticate_Response.

In one embodiment, message #1010 may be used as an example of the first message.

S1011: The AMF adds/updates information in the stored data of the UE to indicate the user currently using the UE.

Exemplarily, the UE data stored by the AMF may include UE context information. Based on the UE identifier, the AMF may search for the UE context from its stored UE context. Information may be added/updated in the UE context to indicate the user currently using the UE. For example, assuming the user identifier of the user is user ID#2, the words "current user: user ID#2" may be added to the UE context information to indicate the user currently using the UE.

In one embodiment, step S1011 may correspond to step S403.

S1012, AMF sends message #1012; accordingly, UE receives the message.

The AMF may send a message to the UE to notify the user currently using the UE that the UE has successfully registered with the network. Message #1012 may include the user ID.

Step S1012 may correspond to step S406 .

In an embodiment of the present application, the AMF can store the identifier of the user currently using the UE. In this way, the AMF can pass the recorded user identifier to other network elements, enabling the UDM and UDR to accurately provide services to the user based on the user identifier. In this way, during the establishment of the PDU session, signaling overhead can be reduced and communication efficiency can be improved.

For example, the following still takes AUSF as the second network element and AMF as the first network element as an example, and introduces the process of establishing a PDU session in combination with Figure 11.

FIG11 is a flow chart of another communication method provided by an embodiment of the present application. The method 1100 may include the following steps:

S1101, UE sends message #1101; accordingly, AMF receives the message.

Message #1101 may be used to request the establishment of a PDU session and may include an identifier of the PDU session.

In one embodiment, message #1101 may be used as an example of a second request message.

S1102, AMF selects SMF.

Exemplarily, steps S1101 and S1102 may correspond to steps S901 and S902.

S1103, AMF confirms the user ID of the user currently using the UE based on the stored context of the UE.

S1104, AMF sends message #1104; accordingly, SMF receives the message.

Message #1104 may include the identifier of the PDU session, the SUPI, and the user ID of the user currently using the UE.

In one embodiment, message #1104 may serve as an example of a third request message.

S1105, SMF sends message #1105; accordingly, UDM receives the message.

Message #1105 may include the user ID of the user currently using the UE. Message #1104 may be used to query the user's subscription data and may be recorded as Nudm_SDM_Get.

Based on the user ID, the UDM can search for the user file associated with the user ID from its stored user files. The user file may include contract data.

S1106, UDM sends message #1106; correspondingly, SMF receives the message.

Message #1106 may include a user file of the user currently using the UE, and the user file may include subscription data of the user.

S1107, SMF sends message #1107; accordingly, AMF receives the message.

The SMF can determine whether to allow the establishment of a PDU session based on the user's subscription data. When the establishment of a PDU session is allowed, the SMF can create a session management context for the PDU session.

Message #1107 may include an identifier of the session management context of the PDU session.

In some possible implementations, S1108 , the PDU session is authenticated.

The SMF can determine whether a secondary authentication is required for the PDU session based on the user's subscription data and/or the session management policy associated with the DN. If a secondary authentication is not required for the PDU session, step S1108 can be skipped.

S1109: The SMF selects a suitable PCF.

Exemplarily, steps S1107 to S1109 may correspond to steps S907 to S909.

S1110, SMF sends message #1110; accordingly, PCF receives the message.

Message #1110 may include the SUPI, the user ID of the user currently using the UE, and the identifier of the PDU session.

Message #1110 may be used to request an update of a session management control policy and may be recorded as Npcf_SMPolicyControl_Update_Request.

S1111, PCF sends message #1111; accordingly, UDR receives the message.

If the PCF does not store subscription data associated with the user ID of the user currently using the UE, the PCF may send a message to the UDR to query the subscription data associated with the user ID. Message #1111 may be recorded as Nudr_DM_Query_Request.

In one embodiment, message #1111 may include the user ID of the user currently using the UE. Accordingly, the UDR may query data related to the user based on the user ID.

Exemplarily, when a session management policy related to a user currently using the UE is stored in the PCF, steps S1111 and S1112 may be skipped.

S1112, UDR sends message #1112; accordingly, PCF receives the message.

The UDR can query the relevant data of the user currently using the UE from the data stored therein.

Message #1112 may include session management control policy information of the PDU session, such as user level, maximum aggregate bit rate of the QoS flow corresponding to DNN/S-NSSAI, allowed services, etc.

S1113, PCF determines to update the policy associated with the PDU session, or determines to send a new policy to SMF.

S1114, PCF sends message #1114; accordingly, SMF receives the message.

Message #1114 may include session control policy information for the PDU session corresponding to the user ID of the user.

Message #1114 may include a response message to message #1110, which may be recorded as Npcf_SMPolicyControl_Update_Response.

S1115, SMF selects appropriate UPF.

S1116: Establish a PDU session.

In one embodiment, steps S1113 to S1116 may correspond to steps S913 to S916.

For example, the process of AMF selecting SMF is described below in conjunction with Figure 12.

FIG12 is a flow chart of another communication method provided by an embodiment of the present application. The method 1200 may include the following steps:

S1201, AMF sends message #1201 to NSSF.

The AMF can send a message to the NSSF in the serving PLMN to query the NRF instance of the network slice serving the UE. Message #1201 can be recorded as Nnssf_NSSelection_Get.

The S-NSSAI of the visited PLMN (VPLMN) is derived from the allowed NSSAI requested by the UE, the PLMN ID of the SUPI, and the tracking area identity (TAI) of the UE, and indicates the request during the PDU session establishment process in non-roaming or roaming with local offload scenarios.

S1202, NSSF sends message #1202 to AMF.

The NSSF in the serving PLMN selects a network slice instance, determines and returns an appropriate NRF. This NRF can be used to select network elements or services within the selected network slice instance. Optionally, it returns the ID of the network-specific identifier (NSI) corresponding to the network slice instance.

Message #1202 may include a response message to message #1201. Message #1202 may be recorded as Nnssf_NSSelection_Get_response.

In one embodiment, when the AMF has obtained the NRF within the network slice instance in the PDU session based on configuration information or based on network slice selection information received during the registration process, steps S1201 and S1202 can be skipped.

S1203, AMF sends message #1203; accordingly, NRF receives the message.

The AMF may send a message to query the appropriate NRF in the serving PLMN.

Message #1203 may be denoted as Nnrf_NFDiscoverry_Requst and may include the S-NSSAI of the VPLMN of the PDU session, the allowed NSSAI, and the PLMN ID of the SUPI.

In some possible implementations, message #1203 may also include the NSI ID when the AMF has stored the NSI ID of the CPLMN's S-NSSAI for this PDU session from the allowed NSSAIs.

S1204, NRF sends #1204; accordingly, AMF receives the message.

The NRF in the serving PLMN may send a message to provide the AMF with the set of discovered SMF instances or the set of endpoint addresses of SMF service instances, and possibly the corresponding S-NSSAI for subsequent NRF queries. For example, the endpoint address may include an IP address or a fully qualified domain name (FQDN).

Message #1204 may include a response message to message #1203, which may be recorded as Nnrf_NFDiscoverry_Requst_response.

In one embodiment, through steps S1201 to S1204, the AMF can obtain information about the SMF and select an appropriate SMF.

In another embodiment, when the AMF stores information of available SMF, steps S1201 to S1204 may be skipped.

Exemplarily, the following describes the association process of the session management policy with reference to FIG13 .

Figure 13 is a flow chart of another communication method provided by an embodiment of the present application. Method 1300 may include the following steps.

S1301, SMF sends message #1301 to PCF.

In one embodiment, when it is determined that PCC authorization is required, the SMF may send a message to the PCF to request the creation of a session management policy association. For example, in this scenario, steps S1301 to S1306 may correspond to step S208.

In another embodiment, the SMF may send a message to the PCF to request an update of the session management policy. For example, in this scenario, step S1301 may correspond to step S910 or S1110.

S1302, PCF sends message #1302 to UDR.

When the PCF does not store the required UE-related subscription information and the required user ID-related subscription information, it can query the UDR for the required information.

In one embodiment, message #1302 may include a data key and a data set. The data key may include an identifier for querying data, such as a SUPI, user ID, etc. The data set may include the data to be queried. For example, Table 1 shows a storage format for a UDR.

Table 1 Data format stored in UDR

S1303, UDR sends message #1303 to PCF.

For example, the UDR can query the corresponding contract data based on data and data set and send it to the PCF.

S1304, perform expenditure limit report retrieval.

A policy counter is set in the charging function (CHF) network element. The PCF can initiate the retrieval of the required expenditure limit report based on the status of the policy counter.

In one embodiment, an initial spending limit report retrieval may be initiated when a policy counter status report is not established for the subscribing user.

In yet another embodiment, when a policy counter status report has been established for a subscribing user and the PCF determines that the status of an additional policy counter is required, the PCF may initiate an interim spending limit report retrieval.

S1305: Determine the strategy.

In one embodiment, the PCF may establish a session management policy association.

In another embodiment, the PCF may update the session management policy association.

S1306, PCF sends message #1306 to SMF.

Message #1306 may be a response message to message #1301. Message #1306 may include information about a session management policy of the PDU session.

The method provided in the embodiment of the present application is described in detail above in conjunction with Figures 4 to 13. Below, the apparatus provided in the embodiment of the present application is described in detail in conjunction with Figures 14 and 15. It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment. Therefore, for matters not described in detail, please refer to the method embodiment above. For the sake of brevity, it will not be repeated here.

Figure 14 is a schematic block diagram of an apparatus provided in an embodiment of the present application. Apparatus 1400 may correspond to a first network element, a second network element, a third network element, an SMF, or a PCF, or may be a component (e.g., a chip, a processor, or a processing circuit) or unit that implements the functions of the aforementioned network elements.

Optionally, the device 1400 may include a communication module 1410, which may also be called a transceiver module, a transceiver, a transceiver, or a transceiver device, etc., for performing receiving (or inputting) and/or sending (or outputting) operations.

In one embodiment, when the device 1400 is a first network element, or a device applied to a first network element, the communication module 1410 can be used to receive a first message, send a first request message, etc.

In another embodiment, when the device 1400 is a second network element, or a device applied to a second network element, the communication module 1410 can be used to send the first message.

In another embodiment, when the device 1400 is a third network element, or a device applied to a third network element, the communication module 1410 can be used to receive the first request message, send the fourth message, etc.

In another embodiment, when the device 1400 is an SMF, or a device applied to an SMF, the communication module 1410 can be used to send a second message, receive a third message, etc.

In another embodiment, when the device 1400 is a PCF, or a device applied to a PCF, the communication module 1410 can be used to send the fourth request message and receive the fifth message.

Optionally, the apparatus 1400 may include a processing module 1420 , which may be a processor, a processing board, a processing unit, or a processing device.

In one embodiment, when the apparatus 1400 is a first network element, or is an apparatus applied to a first network element, the processing module 1420 may be configured to determine a user identifier of an activated user of the terminal device according to an identifier of the terminal device.

In another embodiment, when the apparatus 1400 is a third network element, or is an apparatus applied to a third network element, the processing module 1420 may be configured to determine the user identification of the activated user of the terminal device according to the identification of the terminal device.

Optionally, the apparatus 1400 may include a storage module 1430. The storage module may be a memory, a storage unit, or a storage device.

In one embodiment, when the device 1400 is a first network element, or a device applied to a first network element, the storage module 1430 can be used to determine and store a corresponding user identifier according to the first message.

In another embodiment, when the device 1400 is a third network element, or a device applied to a third network element, the storage module 1430 can be used to update the contract information of the terminal device stored in the third network element according to the first request information.

Figure 15 is a schematic block diagram of an apparatus 2000 provided in an embodiment of the present application. The apparatus 2000 includes at least one processor 2010 to implement the functions of the first network element, the second network element, the third network element, the SMF, or the PCF described in the aforementioned method embodiment.

Optionally, the processor 2010 is coupled to a memory, which may be located within the device, integrated with the processor, or external to the device. The device 2000 may further include at least one memory 2020. The memory 2020 stores computer programs, instructions, or data necessary to implement any of the above-described method embodiments. The processor 2010 may execute the computer programs, instructions, or data stored in the memory 2020 to perform the interleaving method or deinterleaving method of any of the above-described embodiments.

Optionally, the apparatus 2000 may further include a communication interface 2030, and the apparatus 2000 may exchange information with other devices via the communication interface 2030. Exemplarily, the communication interface 2030 may be a transceiver, circuit, bus, module, pin, or other type of interface.

Coupling in this application refers to an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, and is used for information exchange between devices, units, or modules. The processor 2010 may operate in conjunction with the memory 2020 and the communication interface 2030. The specific connection medium between the processor 2010, memory 2020, and communication interface 2030 is not limited in this application.

As shown in Figure 16, the present application also provides a chip (or chip system). The chip (or chip system) 30 may include a circuit 31 and an input/input interface 32. The circuit 31 may be a logic circuit, an integrated circuit, etc., and the input/output interface 32 may also be an input/output circuit, or an interface circuit, which can input information (or receive information) and output information (or send information). Optionally, the chip system can be composed of chips, or it can include chips and other discrete devices. The chip 30 can be used to execute the methods performed by the first network element, the second network element, the third network element, the SMF or the PCF in each embodiment of the present application.

In addition, the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the operations and/or processing performed by the first network element, the second network element, the third network element, the SMF or the PCF in the various method embodiments of the present application are executed.

The present application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are run on a computer, the operations and/or processing performed by the first network element, the second network element, the third network element, the SMF or the PCF in the various method embodiments of the present application are executed.

In addition, the present application further provides a chip, comprising a processor. A memory for storing a computer program is provided independently of the chip, and the processor is configured to execute the computer program stored in the memory, so that the operations and/or processes performed by the first network element, the second network element, the third network element, the SMF, or the PCF in any one of the method embodiments are executed.

Furthermore, the chip may further include a communication interface. The communication interface may be an input/output interface, or an interface circuit, etc. Furthermore, the chip may further include a memory.

The present application provides a communication system, including one or more of the first network element, the second network element, the third network element, the SMF and the PCF in the above method embodiment.

In this application, a processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in this application. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in this application may be directly executed by a hardware processor, or by a combination of hardware and software modules within the processor.

The memory may be a non-volatile memory, such as a hard disk or solid-state drive, or a volatile memory, such as a random access memory. A memory is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in this application may also be a circuit or any other device capable of performing a storage function, for storing program instructions and/or data.

Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.

The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims (25)

A communication method, characterized in that it is configured to be executed in a first network element, the method comprising: receiving a first message indicating successful authentication of an activated user of a terminal device, the first message including a user identifier of the activated user; According to the first message, the user identifier is stored. The method according to claim 1, further comprising: A first request message is sent, where the first request message is used to request updating of the contract information of the terminal device, and the first request message includes the user identifier and the identifier of the terminal device. The method according to claim 2, further comprising: receiving a second message, where the second message is used to query the contract information of the terminal device; A third message is sent, where the third message includes the contract information associated with the user identifier. The method according to claim 3, characterized in that the third message includes the user identification. The method according to any one of claims 2 to 4, characterized in that the first network element comprises a unified data management network element. The method according to claim 1, further comprising: receiving a second request message, where the second request message is used to request establishment of a protocol data unit (PDU) session for the terminal device, and the second request message includes an identifier of the terminal device; Determining the user identification according to the identification of the terminal device; Send a third request message, where the third request message is used to request creation of a session management context for the PDU session, and the third request message includes an identifier of the PDU session, an identifier of the terminal device, and the user identifier. The method according to claim 6 is characterized in that the first network element includes a mobility management function network element. The method according to any one of claims 1 to 7, wherein the first network element stores the context of the terminal device or the subscription information of the terminal device, and the storing the user identifier according to the first message comprises: According to the first message, the user identifier is stored in the context of the terminal device or the contract information of the terminal device. A communication method, characterized in that it is configured to be executed in a second network element, the method comprising: When the authentication of the activated user of the terminal device is successful, a first message is sent, where the first message indicates the successful authentication of the activated user of the terminal device and includes a user identifier of the activated user. A communication method, characterized in that it is configured to be executed in a third network element, the method comprising: Receive a first request message, where the first request message is used to request updating the contract information of the terminal device, and the first request message includes a user identifier of an activated user of the terminal device and an identifier of the terminal device; According to the first request information, the contract information of the terminal device stored in the third network element is updated. The method according to claim 10, further comprising: A fourth message is sent, where the fourth message is used to indicate that the contract information of the terminal device has been updated. The method according to claim 10 or 11, wherein the contract information includes session management control policy information, and the method further comprises: receiving a fourth request message, where the fourth request message is used to request the session management control policy information associated with the terminal device, and the fourth request message includes an identifier of the terminal device; Determining the user identification according to the identification of the terminal device; A fifth message is sent, where the fifth message includes the session management control policy information associated with the user identifier. The method according to claim 10 or 11, wherein the contract information includes session management control policy information, and the method further comprises: receiving a fifth request message, the fifth request message being used to request the session management control policy information associated with the user identifier, the fifth request message including the user identifier; A sixth message is sent, where the sixth message includes the session management control policy information associated with the user identifier. A communication method, characterized in that it is configured to be executed in a session management function network element, the method comprising: Sending a second message, where the second message is used to query the contract information of the terminal device, and the second message includes an identifier of the terminal device; A third message is received, where the third message includes contract information associated with a user identifier of an activated user of the terminal device, where the user identifier is determined based on an identifier of the terminal device. The method according to claim 14, characterized in that the third message also includes the user identification. The method according to claim 14 or 15, characterized in that the method further comprises: Sending a sixth request message, where the sixth request message is used to request updating session management control policy information for the PDU session of the terminal device, the sixth request message including an identifier of the terminal device and an identifier of the PDU session; A seventh message is received, where the seventh message includes session management control policy information associated with the user identifier. The method according to claim 16, characterized in that the sixth request information also includes the user identifier. The method according to any one of claims 14 to 17, further comprising: Determine whether to perform secondary authentication based on the contract information associated with the user identifier. A communication method, characterized in that it is used to be executed in a policy control function network element, the method comprising: Sending a fourth request message, where the fourth request message is used to request session management control policy information associated with the terminal device, and the fourth request message includes an identifier of the terminal device; A fifth message is received, where the fifth message includes session management control policy information associated with a user identifier of an activated user of the terminal device. A communication device, characterized by comprising a module or unit for executing the method according to any one of claims 1 to 19. A communication device, characterized in that it includes at least one processor, the at least one processor is coupled to at least one memory, and the at least one processor is used to execute a computer program or instruction stored in the at least one memory so that the device performs the method according to any one of claims 1 to 19. A chip, characterized in that it includes a circuit and a communication interface, wherein the communication interface is used to receive information from other devices and input it into the circuit, and/or the communication interface is used to send information in the circuit to other devices, and the circuit is used to execute the method as described in any one of claims 1 to 19. A communication system, characterized by comprising one or more of a first network element, a second network element, a third network element, a session management function network element, and a policy control function network element; The first network element is configured to perform the method according to any one of claims 1 to 8; The second network element is configured to perform the method according to claim 9; The third network element is configured to perform the method according to any one of claims 10 to 13; The session management function network element is used to perform the method according to any one of claims 14 to 18; The policy control function network element is used to execute the method according to claim 19. A computer-readable storage medium, characterized in that instructions or program codes are stored thereon, and when the instructions or program codes are executed by a processor, the processor implements the method according to any one of claims 1 to 19. A computer program product, characterized in that the computer program product comprises: computer program code, and when the computer program code is executed, it implements the method according to any one of claims 1 to 19.