Communication method, and device
By sending a first identifier through the terminal device to indicate relevant information for dynamic adjustment of network configuration, the problem of inflexible adjustment of configuration information in the prior art is solved, and more accurate configuration adaptation is achieved.
Patent Information
- Application Number
- PCT/CN2023/098088
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-06-02
- Publication Date
- 2024-12-05
AI Technical Summary
In existing technologies, the configuration information of terminal devices cannot be flexibly and accurately adjusted according to the fine-grained needs of different users and applications, resulting in network configurations that cannot meet personalized requirements.
The terminal device sends a first identifier, indicating information related to the terminal device, such as user information, application information, or service information, so that the network device can determine the associated configuration information.
It enables dynamic adjustment of configuration information based on the user and application status of terminal devices, improving the flexibility and accuracy of configuration and meeting the differentiated needs of different users and services.
Smart Images

Figure CN2023098088_05122024_PF_FP_ABST
Abstract
Description
Communication method and device Technical Field
[0001] The present application relates to the field of communications, and more specifically, to a communication method, device, computer-readable storage medium, computer program product, and computer program. Background Art
[0002] In related technologies, configuration information such as subscription information, UE policies, and generated context information is all based on the terminal device's UE (User Equipment) ID (Identity). However, how to more flexibly and accurately adjust or determine more fine-grained (or finer-dimensional) configuration information for terminal devices has become a problem that needs to be solved.
[0003] Summary of the Invention
[0004] Embodiments of the present application provide a communication method, device, computer-readable storage medium, computer program product, and computer program.
[0005] An embodiment of the present application provides a communication method, including:
[0006] The terminal device sends a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about the user using the terminal device, information about the application running on the terminal device, and information about the service running on the terminal device. The first identifier is used to determine the configuration information associated with the first identifier.
[0007] An embodiment of the present application provides a communication method, including:
[0008] A first network device receives a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about a user using the terminal device, information about an application running on the terminal device, and information about a service running on the terminal device. The first identifier is used to determine configuration information associated with the first identifier.
[0009] An embodiment of the present application provides a terminal device, including:
[0010] A first communication unit is used to send a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about a user using the terminal device, information about an application running on the terminal device, and information about a service running on the terminal device. The first identifier is used to determine configuration information associated with the first identifier.
[0011] An embodiment of the present application provides a first network device, including:
[0012] A second communication unit is used to receive a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about a user using the terminal device, information about an application running on the terminal device, and information about a service running on the terminal device. The first identifier is used to determine configuration information associated with the first identifier.
[0013] An embodiment of the present application provides a terminal device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the above method.
[0014] An embodiment of the present application provides a first network device, comprising a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the first network device executes the above method.
[0015] The embodiment of the present application provides a chip for implementing the above method.
[0016] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method.
[0017] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a device to perform the above method when the computer program is executed by the device.
[0018] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above method.
[0019] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method.
[0020] By adopting the solution provided in this embodiment, the terminal device can send a first identifier, which is used to indicate information related to the terminal device. The information related to the terminal device may include at least one of information about the user using the terminal device, information about the application and / or service running on the terminal device, etc., so that the configuration information associated with it can be obtained based on the first identifier. In this way, the network side can determine the configuration information associated with the terminal device based on the information related to the user and / or service and / or application of the terminal device, avoiding the problem in related technologies that it is impossible to flexibly and accurately adjust or determine the corresponding configuration information with finer granularity (or dimensions) such as different users and / or different applications and / or different services. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.
[0022] Figure 2 is a schematic diagram of the 5GC system.
[0023] FIG3 is a schematic diagram of the QoS mechanism in the network architecture of the relevant protocols.
[0024] FIG4 is a schematic diagram of a scenario in which different users of the same UE correspond to different network configurations.
[0025] FIG5 is a schematic flowchart of a communication method according to an embodiment of the present application.
[0026] FIG6 is a schematic flowchart of a communication method according to another embodiment of the present application.
[0027] 7 to 10 are various exemplary flow charts of the processing flow of the communication method according to the embodiments of the present application.
[0028] FIG11 is a schematic block diagram of a terminal device according to an embodiment of the present application.
[0029] FIG12 is a schematic block diagram of a first network device according to an embodiment of the present application.
[0030] FIG13 is a schematic block diagram of a communication device according to an embodiment of the present application.
[0031] FIG14 is a schematic block diagram of a chip according to an embodiment of the present application.
[0032] FIG15 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION
[0033] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.
[0034] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
[0035] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, and the embodiments of the present application may also be applied to these communication systems. In one possible implementation, the communication system in the embodiment of the present application may be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) networking scenario. In one possible implementation, the communication system in the embodiment of the present application may be applied to an unlicensed spectrum, where the unlicensed spectrum may also be considered a shared spectrum; or, the communication system in the embodiment of the present application may also be applied to an authorized spectrum, where the authorized spectrum may also be considered a non-shared spectrum.
[0036] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, where the terminal device may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc. The terminal device may be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a next-generation communication system such as a NR network, or a terminal device in a future-evolved Public Land Mobile Network (PLMN) network, etc. In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as a ship, etc.); it can also be deployed in the air (such as an airplane, a balloon, and a satellite, etc.). In an embodiment of the present application, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc. As an example and not a limitation, in an embodiment of the present application, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices developed by applying wearable technology to intelligently design everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into clothing or accessories. Wearable devices are more than just hardware devices; they also enable powerful functionality through software support, data interaction, and cloud-based interaction.In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0037] In an embodiment of the present application, a network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in a WLAN, a base station (BTS) in a GSM or CDMA, a base station (NodeB, NB) in a WCDMA, an evolved base station (eNB or eNodeB) in an LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network. As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water. In an embodiment of the present application, the network device may provide services for a cell, and the terminal device may communicate with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
[0038] Figure 1 exemplarily shows a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In a possible implementation, the communication system 100 may include multiple network devices 110, and each network device 110 may include other number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application. In a possible implementation, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application. Among them, the network device may include an access network device and a core network device. That is, the wireless communication system also includes multiple core networks for communicating with the access network device. The access network equipment may be an evolutionary base station (evolutional node B, which may be referred to as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), micro base station, access point (AP), transmission point (TP) or new generation Node B (gNodeB) in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system. It should be understood that the equipment with communication functions in the network / system in the embodiment of the present application may be referred to as communication equipment. Taking the communication system shown in Figure 1 as an example, the communication equipment may include network equipment and terminal equipment with communication functions. The network equipment and terminal equipment may be specific equipment in the embodiment of the present application, which will not be repeated here; the communication equipment may also include other equipment in the communication system, such as network controllers, mobile management entities and other network entities, which are not limited in the embodiment of the present application.
[0039] To facilitate understanding of the embodiments of the present application, the following briefly describes the basic processes and basic concepts involved in the embodiments of the present application. It should be understood that the basic processes and basic concepts introduced below do not limit the embodiments of the present application.
[0040] The 5G network system architecture is shown in Figure 2, which includes: NSSF (Network Slice Selection Function) is mainly used to manage network slice related information, such as selecting network slices for terminal devices; AUSF (Authentication Server Function) is used to complete the identity authentication function of user access; UDM (Unified Data Management) is used to manage and store contract data and authentication data; AMF (Access and Mobility Management Function) is used to complete mobility management, security anchor and security context management, etc. In addition to managing the mobility of UE, AMF is also responsible for forwarding session management related messages between UE and SMF; SMF (Session Management Function) is used to complete session management, UE IP address allocation and management, etc.; PCF (Policy Control Function) is responsible for formulating policies related to UE mobility management, session management, billing, etc.; AF (Application Function) is used for external application servers; UPF (User Plane Function) is used to manage and store user data and authentication data; The 5GC (5G Core Network) is a 5G core network that is used for complex user plane processing, such as forwarding traffic between the radio access network and the Internet, reporting traffic usage, and implementing QoS (Quality of Service) policies. The DN (Data Network) is the external data network of the 5GC (such as the Internet). Data is transmitted between the various nodes of the 5GC (5G Core Network), between the user equipment (UE) and the 5GC nodes, between the UE and the Radio Access Network (RAN), and between the RAN and the 5GC nodes through corresponding interfaces. For example, as shown in Figure 2: Data is transmitted between the AMF and NSSF in the 5GC through interface N22; the AMF transmits data to the SMF through interface N11; the AMF transmits data to the AUSF through N12; and the AMF transmits data to the UDM through interface N8. Data is transmitted between the SMF and the UPF through interface N4. The UPF transmits data to the external data network through interface N6 and to the AN through interface N3. The UE establishes an access layer connection with the AN through the Uu port, exchanges access layer messages and wireless data transmission, and establishes a non-access layer (NAS) connection with the AMF through the N1 port, exchanges NAS messages.Data is transmitted between the RAN and AMF via the N2 interface, and between the RAN and UPF via the N3 interface. It should be understood that the above description only describes the interfaces between some nodes, and the other interfaces between other 5GC nodes in Figure 2 are not described one by one.
[0041] The QoS mechanism in the network architecture of the relevant protocols is as follows: The core network element (SMF) determines the PCC rules based on policy information, subscription information, and local configuration, and generates QoS rules, PDRs (Packet Detection Rules), and QoS parameters based on the PCC rules. QoS rules are used on the UE side to bind uplink service data flows to QoS flows, while PDRs are used on the UPF side to bind downlink service data flows to QoS flows. QoS parameters are used to generate parameters for each QoS flow. QoS parameters are sent to the RAN side to generate the DRB corresponding to the QoS flow, ensuring end-to-end transmission quality (guaranteeing the air interface and core network side). With reference to Figure 3, during uplink transmission, the UE receives data packets from applications, maps them to QoS flows based on QoS rules, and applies QoS flow markings. The UE then marks all packets in the QoS flow with the same QFI, maps the QoS flow to AN resources, and sends it to the AN. The RAN (i.e., the AN shown in Figure 3) converts the QoS flows mapped to AN resources (i.e., the AN resources corresponding to each QoS flow generated by the AN based on QoS parameters) into PDU sessions and sends them to the UPF. During downlink transmission, the PDF receives data packets from applications, classifies them based on the PDR, performs QoS flow markings, and other operations, marks all packets in the QoS flow with the same QFI, combines the QoS flows into PDU sessions, and sends the PDU sessions to the RAN (i.e., the AN shown in Figure 3). The RAN then transmits the received PDU (Protocol Data Unit) sessions to the UE via AN resources.
[0042] Subscription information, UE policies, and generated context information in relevant protocols are all implemented based on the UE ID. However, even with the same UE ID, a terminal may be used by different users at different times (i.e., the User ID may be different). Different users may have different network requirements due to service preferences, but 3GPP networks cannot distinguish this functionality. For the same UE, changing the corresponding communication network configuration (referred to as the network configuration) when the user using the UE changes to meet the differentiated needs of different users or services is not possible under current mechanisms. Configuration is a general term that can be understood as network subscription information, policy information, and other information that changes with each user. Consequently, the core network needs to adjust its access and mobility management context, UE policies, session management context, and other information. For example, referring to Figure 4, the users using a UE may be User-1, User-2, and User-3. However, if User-1 can use Network Configuration-1, User-2 can use Network Configuration-2, and User-3 can use Network Configuration-3, this is not possible with current technologies.
[0043] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the objects associated before and after are in an "or" relationship. It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B. In the description of the embodiments of this application, the term "corresponding" can mean that there is a direct or indirect correspondence between the two, or it can mean that there is an association relationship between the two, or it can mean a relationship between indication and indication, configuration and configuration, etc.
[0044] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.
[0045] Figure 5 is a schematic flow chart of a communication method according to an embodiment of the present application. The method includes at least part of the following contents.
[0046] S510. The terminal device sends a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about a user using the terminal device, information about an application running on the terminal device, and information about a service running on the terminal device. The first identifier is used to determine configuration information associated with the first identifier.
[0047] Figure 6 is a schematic flow chart of a communication method according to another embodiment of the present application. The method includes at least part of the following contents.
[0048] S610. The first network device receives a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about a user using the terminal device, information about an application running on the terminal device, and information about a service running on the terminal device. The first identifier is used to determine configuration information associated with the first identifier.
[0049] Here, the first network device may be any device on the network side. In one embodiment, the network side may include at least an access network side and a core network side. In this case, the first network device may be a first access network device or a first core network device. In one embodiment, the network side includes a core network side. In this case, the first network device may be a first core network device.
[0050] The aforementioned first core network device may be an access and mobility management function (AMF) or a session management function (SMF). It should be understood that the above is merely an exemplary description. In actual processing, the aforementioned first core network device is not limited to the core network elements listed above, and all possible network elements of the first core network device are not exhaustively listed here.
[0051] The first identifier may be a value under the first category of identifiers. The first category of identifiers is different from permanent identifiers in related technologies. In some embodiments, the permanent identifier may include, but is not limited to, at least one of the following: SUPI (Subscription Permanent Identifier), SUCI (Subscription Concealed Identifier), PEI (Permanent Equipment Identifier), 5G-GUTI (5G Globally Unique Temporary Identifier), Internal-Group Identifier (IGI), GPSI (Generic Public Subscription Identifier), etc. SUPI is a globally unique 5G user permanent identifier that should be assigned to each user in the 5G system and configured in the UDM / UDR. SUPI is only used within the 3GPP system. SUPI may include: IMSI (International Mobile Subscriber Identity), or a network-specific identifier that can be used for a private network. SUCI is a privacy-preserving identifier that includes a hidden SUPI. The format supported by the PEI parameter is IMEI (International Mobile Station Equipment Identity).
[0052] The first type of identifier is used to indicate at least one of a user, an application, and a service. Accordingly, the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about the user using the terminal device, information about the application running on the terminal device, and information about the service running on the terminal device.
[0053] In some embodiments, the first identifier is used to indicate information about an application running on the terminal device and / or information about a service running on the terminal device.
[0054] Here, the application information may refer to an identification of the application, which may include at least one of the following: an application name, an application ID, an application number, etc. The service information may refer to an identification of the service, which may include at least one of the following: a service name, a service ID, a service number, etc.
[0055] The first identifier is used to indicate information about the application running on the terminal device, which may refer to the first identifier being a first value, and the first value being used to indicate information about the application running on the terminal device, such as the first value being equal to the identifier of the application running on the terminal device, or the first value being associated with the identifier of the application running on the terminal device, or the first value having a corresponding relationship with the identifier of the application running on the terminal device. The first identifier is used to indicate information about the service running on the terminal device, which may refer to the first identifier being a first value, and the first value being used to indicate information about the service running on the terminal device, such as the first value being equal to the identifier of the service running on the terminal device, or the first value being associated with the identifier of the service running on the terminal device, or the first value having a corresponding relationship with the identifier of the service running on the terminal device.
[0056] In some embodiments, the first identifier is used to indicate information about a user using the terminal device. The information about the user using the terminal device includes at least one of the following: an identifier of the user using the terminal device, or biometric information of the user using the terminal device.
[0057] Here, the user information may be an identification of the user, for example, may be represented as a user ID.
[0058] The biometric information may include at least one of the following: fingerprint, facial features, and voice features. The biometric information may refer to at least one of the specific feature information of a fingerprint, facial features, and voice features, or the biometric information may refer to at least one of a fingerprint ID, facial feature ID, and voice feature ID. For example, the biometric information may also be referred to as biometric information. Hereinafter, unless otherwise specified, biometric information and biometric information have the same meaning.
[0059] For example, the first identifier is used to indicate the information of the user using the terminal device, which may mean that the first identifier is a first value, and the first value is used to indicate the information of the user using the terminal device. For example, the first value is equal to the identifier of the user using the terminal device, or the first value is associated with the identifier of the user using the terminal device, or the first value has a corresponding relationship with the user's identifier, or the first value is equal to the fingerprint ID of the user using the terminal device, or the first value is associated with the fingerprint ID of the user using the terminal device, or the first value has a corresponding relationship with the user's fingerprint (or fingerprint ID), etc. All possible situations are not enumerated here.
[0060] The foregoing embodiment has described that the first identifier may be a first identifier under the first category of identifiers, and the first identifier may vary depending on at least one of the user using the terminal device, the application running on the terminal device, and the service running on the terminal device. The first identifier may vary depending on at least one of the user using the terminal device, the application running on the terminal device, and the service running on the terminal device, which may mean that different values of the first identifier are used to indicate at least one of the following: different users using the terminal device, different applications running on the terminal device, and different services running on the terminal device.
[0061] The first identifier may include one or more bits, and the number of the bits is not limited in this embodiment. As long as it is greater than or equal to 1, it is within the protection scope of this embodiment. The value of the first identifier is the value of each bit in the one or more bits, that is, the value of each bit in the one or more bits is combined to form the value of the first identifier, and the value can be used to indicate at least one of the user using the terminal device, the application running on the terminal device, and the service running on the terminal device. For example, the number of bits included in the first identifier is 2, and the values of the two bits are 0 and 1 respectively. The value "01" can be used to indicate user A of the terminal device.
[0062] In one example, the first identifier may be a direct indication of specific information. For example, the first identifier includes multiple bits, and the values of each bit in the multiple bits are combined to form the specific information to be indicated. For example, the values of the various bits included in the first identifier are combined to form the value of the first identifier. The value of the first identifier may be the original information of the biometric information, or the compressed information of the biometric information, or the identifier of the App service used in the terminal device.
[0063] In another example, the first identifier may also be a temporary identifier, which may be dynamically updated to the terminal device by the network side, or may be a value pre-configured or pre-negotiated by the terminal device; there is a correspondence between the value of the first identifier and the specific information, and this correspondence may also be statically pre-configured by the terminal device or dynamically assigned to the terminal device by the network. For example, the first identifier includes three bits, the value of the three bits is 001, that is, the value of the first identifier is 001, and the value of the first identifier 001 corresponds to the biometric information fingerprint of user A, that is, the value of the first identifier 001 is used to indicate the biometric information of user A; for another example, the first identifier includes three bits, the value of the three bits is 002, that is, the value of the first identifier 002, and the value of the first identifier 002 corresponds to the biometric information fingerprint of user B, that is, the value of the first identifier 002 is used to indicate the biometric information of user B.
[0064] For example, different values of the first identifier may indicate at least one of different users using the terminal device, different applications (or services) running on the terminal device, etc. For example, when user A uses the terminal device to run application a1, the first identifier is the first value, and the first value is associated with the identifier of user A and the identifier of application a1; for example, when user A uses the terminal device to run service a2, the first identifier is the second value, and the second value is associated with the identifier of user A and the identifier of application a2; for example, when user A uses the terminal device to run application a1, the first identifier is the third value (the third value is associated with the biometric information of user A and the identifier of application a1), and when user B uses the terminal device to run application a1, the first identifier is the fourth value (the fourth value is associated with the identifier of user B and the identifier of application a1). All possible situations are not enumerated here.
[0065] For example, different values of the first identifier are used to indicate the biometric information of different users using the terminal device, or different biometric information of the same user using the terminal device. For example, when different users use the same terminal device, the value of the first identifier will change. For another example, when the same user uses the same terminal device and the user's biometric information (fingerprint, facial features, voice features, etc.) changes, the value of the first identifier will also change.
[0066] In some other examples, the first identifier can also be used to indicate at least one of the following: information about the user corresponding to each device in the device group where the terminal device is located, information about the application running on each device in the device group where the terminal device is located, and information about the service running on each device in the device group where the terminal device is located. In this example, the first identifier can be in the form of a list. For example, when the first identifier is used to indicate information about the user corresponding to each device in the device group where the terminal device is located, the first identifier can be a list containing one or more first sub-identifiers, each of which is used to indicate user information corresponding to a device. All possible representation forms of the first identifier are not exhaustively listed here.
[0067] In some possible examples, the first identifier may also be used to indicate at least one of the following: information about users of other devices associated with the terminal device, information about applications running on other devices associated with the terminal device, and information about services running on other devices associated with the terminal device. Here, the other devices associated with the terminal device may refer to the terminal device acting as a relay device or proxy device for other devices. This does not exhaustively enumerate all possible contents that may be indicated by the first identifier; as long as the first identifier is related to at least one of the user, application, service, etc., it falls within the scope of protection of this embodiment.
[0068] In some possible implementations, the terminal device sending the first identifier may be the terminal device sending the first identifier to the first network device. Correspondingly, the first network device receiving the first identifier means that the first network device receives the first identifier sent by the terminal device.
[0069] In one embodiment, the first network device is a first access network device. In this case, the first identifier can be carried by an AS (Access Stratum) message. In one embodiment, the first network device can be a first core network device. In this case, the first identifier can be carried by a first NAS (Non-Access Stratum) message. The first NAS message can be related to the actual process, that is, the first NAS message can be different when the process is different. In some embodiments, the first identifier is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message. That is, the first NAS message can include at least one of a registration request message, a registration update message, a session establishment request message, and a session modification request message.
[0070] In some embodiments, the first identifier is used to determine the configuration information associated with the first identifier, which may mean that the first identifier is used by the first network device to determine the configuration information associated with the first identifier. In some embodiments, the configuration information may refer to the network configuration. In some embodiments, the configuration information associated with the first identifier includes at least one of the following: the UE policy associated with the first identifier; the contract information associated with the first identifier; the policy rules associated with the first identifier; and one or more electronic devices associated with the first identifier. It should be noted that, among the one or more electronic devices associated with the aforementioned first identifier, the one or more electronic devices may include the aforementioned terminal device.
[0071] In some embodiments, after the first network device receives the first identifier, the method further includes at least one of the following: the first network device sends the first identifier to the second network device, and the first identifier is used by the second network device to determine the UE policy associated with the first identifier; the first network device obtains the policy rules associated with the first identifier from the second network device; the first network device obtains the contract information associated with the first identifier from the third network device; the first network device determines the contract information associated with the first identifier based on the second association relationship, wherein the second association relationship includes the contract information associated with each second identifier in one or more second identifiers; the first network device determines the policy rules associated with the first identifier based on the third association relationship, wherein the third association relationship includes the policy rules associated with each second identifier in one or more second identifiers; the first network device obtains the UE policy associated with the first identifier from the second network device; the first network device determines the UE policy associated with the first identifier based on the first association relationship, wherein the first association relationship includes the UE policy associated with each second identifier in one or more second identifiers.
[0072] The one or more electronic devices associated with the aforementioned first identifier may be determined by the first network device based on a fourth association relationship, where the fourth association relationship includes one or more electronic devices associated with each second identifier in the one or more second identifiers. The fourth association relationship may be pre-stored in the first network device, or may be sent to the first network device by the second network device or the third network device. Alternatively, the one or more electronic devices associated with the aforementioned first identifier may be obtained by the first network device from the second network device or the third network device; the second network device or the third network device may determine the one or more electronic devices associated with the first identifier based on its stored fourth association relationship and send it to the first network device.
[0073] In some possible examples, the second network device and the third network device may be devices (or network elements) on the core network side. In other possible examples, some of the second network device and the third network device may be devices on the core network side, while the rest may not be devices on the core network side. This does not exhaustively list or limit all possible device types of the second network device and the third network device.
[0074] The aforementioned first, second, third, and fourth associations may be first-type associations. This first-type association is different from the second-type association in the relevant protocol. For example, the second-type association may include at least one of the subscription information, policy information, and UE policy associated with the permanent identifier; while the first-type association refers to at least one of the subscription information, policy information, UE policy, and other terminals associated with the first identifier.
[0075] Any of the aforementioned second identifiers is any value under the first category of identifiers. That is, the second identifier and the aforementioned first identifier are both first category identifiers, and different second identifiers can be different values under the first category of identifiers; while the first identifier is a specific value under the first category of identifiers, and this specific value is used to indicate the user using the terminal device and / or the application (and / or service) running on the terminal device.
[0076] The first association relationship may refer to the association relationship between each second identifier and the UE policy, that is, the UE policy corresponding to different values of the first type of identifier. The UE policy may include at least one of the following: Access Network Discovery & Selection Policy (ANDSP), Terminal Route Selection Policy (URSP), 5G Proximity Service Policy (ProSe Policy), V2X (Vehicle to Everything) Policy, ATSSS (Access Traffic Steering, Switching, and Splitting) policy, etc.
[0077] The second association relationship may refer to an association relationship between each second identifier and the contract information, that is, the content of the contract information corresponding to different values of the first type of identifier. The contract information may include but is not limited to at least one of the following: access and access and mobility contract, session management contract, slice selection contract, etc. The access and access and mobility contract (or access and access and mobility contract information) may be obtained during the registration process of the terminal device; the session management contract (or session management contract information) may be obtained during the session establishment process of the terminal device; the slice selection contract (or slice selection contract information) may be obtained during the registration process of the terminal device.
[0078] The third association may be an association between each second identifier and a policy rule, i.e., the content of the policy rule corresponding to different values of the first identifier. The policy rule may also be referred to as policy information, and may be used together with the subscription information and local configuration to obtain various related parameters, such as at least one of a QoS rule, a PDR, and a QoS parameter.
[0079] The fourth association relationship may be an association relationship between each second identifier and one or more electronic devices, that is, which terminals can / are allowed to be used by at least one of the user, service, and application corresponding to any second identifier (or the value of any first-category identifier). In this fourth association relationship, the association relationship between any second identifier and one or more electronic devices may be an association relationship between the second identifier and the identifier of each of the one or more electronic devices. The identifier of any electronic device may be a permanent identifier of the electronic device, such as the SUPI of the electronic device.
[0080] In some embodiments, the above multiple association relationships can be stored in at least one of the first network device, the second network device, and the third network device; different network devices can store different association relationships, or different network devices can store the same association relationships, or different network devices can store at least partially different association relationships.
[0081] In some possible implementations, the first identifier may be carried in the registration request message.
[0082] It should be noted that in addition to carrying the first identifier, the registration request message may also carry other information specified by the relevant protocol. For example, the registration request message may also carry at least one of the following: UE ID (such as IMSI or SUPI), network slice identifier (such as Single Network Slice Selection Assistance information (S-NSSAI, single network slice selection assistance information)), etc.; this embodiment does not exhaustively enumerate the various types of information and functions that may be carried by the registration request message. Among them, the UE ID and / or network slice identifier of the terminal device can be combined with the user id (that is, the aforementioned first identifier) to obtain at least one of the policy information, contract information, etc. associated with the terminal device, or the UE ID and / or network slice identifier of the terminal device can also obtain at least one of the policy information, contract information, etc. separately.
[0083] After receiving the registration request message, the first network device can obtain the first identifier reported by the terminal device from the registration request message. Then, the first network device can perform at least one of the following processes: the first network device sends the first identifier to the second network device, and the first identifier is used by the second network device to determine the UE policy associated with the first identifier; the first network device obtains the UE policy associated with the first identifier from the second network device; the first network device determines the UE policy associated with the first identifier based on the first association relationship; the first network device obtains the contract information associated with the first identifier from the third network device; the first network device determines the contract information associated with the first identifier based on the second association relationship.
[0084] Before the aforementioned first network device sends the first identifier to the second network device, it may also include: the first network device determines the second network device. In some embodiments, the first network device determines the second network device, which may refer to: the first network device determines the second network device corresponding to the first identifier based on the first identifier carried by the registration request message, and / or the first network device determines the second network device corresponding to the terminal device based on the UE ID carried by the registration request message. That is, the first network device can select one from one or more candidate network devices as the second network device. The aforementioned second network device may refer to any one of the one or more candidate network devices that can determine the UE policy, and further, the second network device may be any one of the one or more candidate network devices that stores the aforementioned first association relationship.
[0085] After the terminal device sends the first identifier, the method further includes one of the following: the terminal device receives the UE policy associated with the first identifier; the terminal device determines the UE policy associated with the first identifier based on the first association relationship, wherein the first association relationship includes the UE policy associated with each second identifier of one or more second identifiers. Accordingly, in the processing of the first network device, the method further includes one of the following: the first network device sends the UE policy associated with the first identifier to the terminal device; the first network device sends the first association relationship to the terminal device.
[0086] In some possible examples, after the terminal device sends the first identifier, the method further includes: the terminal device receiving a UE policy associated with the first identifier.
[0087] In some embodiments, the first network device sends the first identifier to the second network device; after receiving the first identifier sent by the first network device, the second network device may determine a second identifier that matches (or is the same as) the first identifier based on the first association relationship, and then use the UE policy associated with the matching second identifier as the UE policy associated with the first identifier. Further, the second network device may send the UE policy associated with the first identifier to the terminal device; accordingly, the terminal device receiving the UE policy associated with the first identifier includes: the terminal device may receive the UE policy associated with the first identifier sent by the second network device.
[0088] The second network device may send the UE policy associated with the first identifier to the terminal device in a UCU (UE Configuration Update) process. It should be understood that this is merely an example. In actual processing, the second network device may also send the UE policy associated with the first identifier to the terminal device in other processes, but this is not an exhaustive list.
[0089] In some embodiments, the first network device sends the first identifier to the second network device; after receiving the first identifier sent by the first network device, the second network device may determine the UE policy associated with the first identifier based on the first association relationship. Further, the second network device may send the UE policy associated with the first identifier to the first network device. The first network device obtains the UE policy associated with the first identifier from the second network device, and then the first network device sends the UE policy associated with the first identifier to the terminal device. The terminal device may receive the UE policy associated with the first identifier sent by the first network device.
[0090] In some embodiments, the first network device sends the first identifier to the second network device; after receiving the first identifier sent by the first network device, the second network device may send the first association relationship to the first network device. The first network device may determine the UE policy associated with the first identifier based on the first association relationship, and the first network device sends the UE policy associated with the first identifier to the terminal device. The terminal device may receive the UE policy associated with the first identifier sent by the first network device.
[0091] In some possible examples, after the terminal device sends the first identifier, the method further includes: the terminal device determining a UE policy associated with the first identifier based on the first association relationship.
[0092] Before the terminal device determines the UE policy associated with the first identifier based on the first association relationship, the method may further include: the terminal device receiving the first association relationship. That is, in this example, the terminal device sends the first identifier via a registration request message for the first time after being powered on, and the terminal device may first receive the first association relationship and then determine the UE policy associated with the first identifier based on the first association relationship.
[0093] In some embodiments, the terminal device may be the first association relationship received from the aforementioned second network device. For example, the first network device sends the first identifier to the second network device; after receiving the first identifier sent by the first network device, the second network device may send the first association relationship saved by itself to the terminal device, that is, the terminal device may receive the first association relationship sent by the second network device. In this example, the second network device may send the first association relationship to the terminal device in the UCU (UE Configuration Update) process. It should be understood that this is only an exemplary explanation. In actual processing, the second network device may also send the first association relationship to the terminal device in other processes, but it is not exhaustive.
[0094] In some embodiments, the terminal device may be the first association relationship received from the aforementioned first network device. For example, the first network device sends the first identifier to the second network device; after receiving the first identifier from the first network device, the second network device may send the first association relationship to the first network device, and the first network device may send the first association relationship to the terminal device.
[0095] In some possible examples, after the first network device receives the first identifier, the method further includes one of the following: the first network device obtains the contract information associated with the first identifier from a third network device; the first network device determines a second identifier that matches (or is the same as) the first identifier based on a second association relationship, and then uses the contract information associated with the matching second identifier as the contract information associated with the first identifier.
[0096] In some embodiments, the first network device obtains the contract information associated with the first identifier from the third network device, including: the first network device sends the first identifier to the third network device, and receives the contract information associated with the first identifier sent by the third network device.
[0097] Before the first network device sends the first identifier to the third network device, it may also include: the first network device determines the third network device. Exemplarily, the first network device determines the third network device, which may refer to: the first network device determines the third network device corresponding to the first identifier based on the first identifier carried by the registration request message, and / or the first network device determines the third network device corresponding to the terminal device based on the UE ID carried by the registration request message. That is, there may be multiple network devices on the core network side, and the first network device may select one from one or more candidate network devices as the third network device. The aforementioned third network device may refer to any one of the one or more candidate network devices that can determine the contract information, and further, the third network device may be any one of the one or more candidate network devices that stores the aforementioned second association relationship.
[0098] The first network device sends the first identifier to the third network device, and receives the contract information associated with the first identifier sent by the third network device, which may include: the first network device sends the first identifier to the third network device; the third network device may, after receiving the first identifier sent by the first network device, determine a second identifier that matches (or is the same as) the first identifier based on a second association relationship, and then use the contract information associated with the matching second identifier as the contract information associated with the first identifier; then the first network device receives the contract information associated with the first identifier sent by the third network device.
[0099] In some embodiments, the first network device determines the contract information associated with the first identifier based on the second association relationship.
[0100] The method may further include: the first network device sending the first identifier to the third network device, and receiving the second association relationship from the third network device. The process of selecting or determining the third network device in this example is the same as that in the previous embodiment and will not be described in detail.
[0101] For example, the first network device sends the first identifier to the third network device; after receiving the first identifier sent by the first network device, the third network device can send the second association relationship to the first network device, and the first network device can determine the second identifier that matches (or is the same as) the first identifier based on the second association relationship, and then use the contract information associated with the matching second identifier as the contract information associated with the first identifier.
[0102] For the above-mentioned implementation method, taking the first network device as AMF, the second network device as PCF, and the third network device as PUF as an example, the UDM, PCF and other core network elements can simultaneously send the above-mentioned various association relationships to the required nodes in one operation (such as AMF obtains the association relationship between each second identifier and the access and mobility management contract, SMF obtains the association relationship between each second identifier and the session management contract information, and the terminal device obtains the association relationship between each second identifier and the UE policy), or the UDM, PCF and other core network elements can only send the content corresponding to the current first identifier to the required node each time.
[0103] In some embodiments, the first network device may store the fourth association relationship. After receiving the first identifier, the first network device may determine one or more electronic devices associated with the first identifier based on the first identifier and the fourth association relationship; determine whether the one or more electronic devices associated with the first identifier include the terminal device; and if so, further obtain configuration information associated with the first identifier. It should be understood that the above description is based solely on the example of the fourth association relationship being stored on the first network device. In some possible embodiments, the fourth association relationship may also be saved in the contract information. For example, the contract information is saved in the third network device, and the fourth association relationship is saved in the contract information. Taking the third network device as UDM as an example, the aforementioned first network device may first send the first identifier to the UDM, and the UDM may determine the one or more electronic devices associated with the first identifier based on the first identifier and the fourth association relationship in the contract information, and then determine whether the one or more electronic devices associated with the first identifier include the terminal device. If included, the first network device may be notified to perform further processing to obtain the configuration information associated with the first identifier, or the contract information associated with the first identifier may be sent directly to the first network device, or the second association relationship may be sent directly to the first network device.
[0104] In some possible implementations, the first identifier may be carried by a registration update message.
[0105] It should be noted that, in addition to carrying the first identifier, the registration update message may also carry other information specified in the relevant protocol, but this embodiment does not list all of them.
[0106] It should also be pointed out that the registration update message may be the first time that the first identifier is carried, or the registration update message may be the second time that the first identifier is carried in the registration request message. For example, after the first identifier is carried by the registration request message, if the first identifier is carried again in the registration update message, the value of the first identifier carried by the registration request message is different from the value of the first identifier carried by the registration update message. For example, if the registration request message carries the first identifier, its value is the first value; after the registration of the terminal device is completed, if the user using the terminal device and / or the application running by the terminal device changes, the value of the first identifier will also change, such as changing to the second value. In this case, the terminal device can send the first identifier again through the registration update message.
[0107] After the first network device receives the registration update message, the first network device may perform at least one of the following processing: the first network device sends the first identifier to the second network device, and the first identifier is used by the second network device to determine the UE policy associated with the first identifier; the first network device obtains the UE policy associated with the first identifier from the second network device; the first network device determines the UE policy associated with the first identifier based on the first association relationship; the first network device obtains the contract information associated with the first identifier from the third network device; the first network device determines the contract information associated with the first identifier based on the second association relationship.
[0108] The detailed description of how the first network device determines the second network device before the first network device sends the first identifier to the second network device is the same as that in the above embodiment and will not be repeated herein.
[0109] In some possible examples, after the terminal device sends the first identifier, the method further includes: the terminal device receiving a UE policy associated with the first identifier.
[0110] Optionally, the terminal device may receive a UE policy associated with the first identifier sent by the second network device. This processing is the same as in the previous embodiment and is not repeated here. Optionally, the terminal device may receive a UE policy associated with the first identifier sent by the first network device. This processing is the same as in the previous embodiment and is not repeated here.
[0111] The difference from the above embodiment is that, after receiving the first identifier, the first network device can first detect whether the first association relationship is saved locally. If not, the first identifier is sent to the second network device, and then any one of the processes in the above embodiment can be performed. If the first network device saves the first association relationship, the first network device can directly determine the UE policy associated with the first identifier based on the first association relationship, and the first network device sends the UE policy associated with the first identifier to the terminal device. That is, the terminal device receives the UE policy associated with the first identifier sent by the first network device.
[0112] In some possible examples, after the terminal device sends the first identifier, the method further includes: the terminal device determining, based on the first association relationship, a UE policy associated with the first identifier. The specific processing of the terminal device determining, based on the first association relationship, the UE policy associated with the first identifier is the same as in the previous embodiment and is not further described.
[0113] Before the terminal device determines the UE policy associated with the first identifier based on the first association relationship, the method may further include: the terminal device receiving the first association relationship. In this example, the possible processing of the terminal device receiving the first association relationship is the same as that in the previous embodiment and will not be repeated.
[0114] In one case, the first registration request message sent by the terminal device after it is turned on does not carry the first identifier, and the terminal device can then send the first identifier in a registration update message, and then receive the first association relationship, and then determine the UE policy associated with the first identifier based on the first association relationship. In another case, the first registration request message sent by the terminal device after it is turned on carries the first identifier, and the terminal device saves the first association relationship after receiving it; then the terminal device can send the first identifier (that is, the first identifier whose value has changed) in a registration update message, and directly determine the UE policy associated with the first identifier based on the first association relationship.
[0115] After receiving the first identifier, the first network device may first detect whether the first association relationship is stored locally. If not, the first identifier is sent to the second network device, and then any of the processes in the aforementioned examples may be performed. If the first network device stores the first association relationship, the first network device sends the first association relationship to the terminal device.
[0116] In some possible examples, after the first network device receives the first identifier, the method further includes one of the following: the first network device obtains the contract information associated with the first identifier from a third network device; the first network device determines the contract information associated with the first identifier based on the second association relationship.
[0117] Optionally, the process of the first network device obtaining the contract information associated with the first identifier from the third network device is the same as that in the above embodiment and will not be described in detail.
[0118] Optionally, the first network device determines the contract information associated with the first identifier based on the second association relationship.
[0119] The method may further include: the first network device sending the first identifier to the third network device, and receiving the second association relationship from the third network device. The process of selecting or determining the third network device in this example is the same as that in the previous embodiment and will not be described in detail.
[0120] In one case, the first registration request message sent by the terminal device after it is turned on does not carry the first identifier, and the terminal device can then send the first identifier in a registration update message. The first network device then sends the first identifier to the third network device, receives the second association relationship sent by the third network device, and determines the contract information associated with the first identifier based on the second association relationship. In another case, the first registration request message sent by the terminal device after it is turned on carries the first identifier, and the first network device sends the first identifier to the third network device, receives the second association relationship sent by the third network device, and saves the second association relationship. The terminal device can then send the first identifier (that is, the first identifier whose value has changed) in a registration update message, and the first network device can directly determine the contract information associated with the first identifier based on the locally saved second association relationship.
[0121] It should also be pointed out that in this embodiment, the contract information associated with the first identifier may include at least one of the following: the access and access and mobility contract associated with the first identifier (or access and access and mobility contract information), and the slice selection contract associated with the first identifier (or slice selection contract information).
[0122] In some possible implementations, the method further includes: the terminal device sending first indication information, wherein the first indication information is used to indicate at least one of the following: the terminal device supports reporting the first identifier, the terminal device is capable of recognizing the first identifier, and the terminal device is capable of processing the first identifier. Correspondingly, the first network device receives the first indication information sent by the terminal device, wherein the first indication information is used to indicate at least one of the following: the terminal device supports reporting the first identifier, the terminal device is capable of recognizing the first identifier, and the terminal device is capable of processing the first identifier.
[0123] The first indication information may be carried by a second NAS message, which may be the same as or different from the first NAS message. In a preferred example, the second NAS message may be a registration request message, that is, the first indication information may be carried by the registration request message.
[0124] The first indication information is used to indicate that the terminal device supports reporting the first identifier, that is, the first indication information can be used to indicate that the terminal supports reporting the first identifier as the type of identifier (that is, supports reporting the first category of identifiers). The first indication information is used to indicate that the terminal device can identify the first identifier, that is, the first indication information can be used to indicate that the terminal has the ability to identify the first identifier as the type of identifier (that is, has the ability to identify the first category of identifiers). The first indication information is used to indicate that the terminal device can process the first identifier, that is, the first indication information can be used to indicate that the terminal has the ability to process the first identifier as the type of identifier (that is, has the ability to process the first category of identifiers).
[0125] Optionally, the first indication information may be sent separately, that is, the registration request message may only carry the first indication information without carrying the aforementioned first identifier.
[0126] The method also includes: the first network device sends a second indication message to the terminal device, wherein the second indication message is used to indicate at least one of the following: the network side supports processing the first identifier (or the network side supports processing the first type of identifier), the network side can identify the first identifier (or the network side can identify the first type of identifier), the network side requests the terminal device to report the first identifier (or the network side requests the terminal device to report the first type of identifier), the network side requires the terminal device to report the first identifier (or the network side requires the terminal device to report the first type of identifier), and the network side allows the terminal device to report the first identifier (or the network side allows the terminal device to report the first type of identifier). Accordingly, the method also includes: the terminal device receives the second indication message.
[0127] In some embodiments, the network side may include an access network and / or a core network side, that is, the second indication information may be sent by the first network device when there is a first network device, a second network device, and a third network device on the access network and / or the core network side, and at least one of the following functions: supporting processing of the first identifier (or supporting processing of the first type of identifier), being able to identify the first identifier (or being able to identify the first type of identifier), requesting the terminal device to report the first identifier (or requesting the terminal device to report the first type of identifier), requiring the terminal device to report the first identifier (or requiring the terminal device to report the first type of identifier), and allowing the terminal device to report the first identifier.
[0128] In some embodiments, when the network side includes an access network, the first network device, the second network device, and the third network device may be different access network devices. In some embodiments, when the network side includes a core network side, the first network device, the second network device, and the third network device may be different core network devices, such as a first core network device, a second core network device, and a third core network device, respectively. In some embodiments, when the network side includes an access network and a core network side, the first network device may be a first access network device or a first core network device, the second network device may be a second access network device or a second core network device, and the third network device may be a third access network device or a third core network device.
[0129] The second indication information may be carried by a third NAS message, which is different from the second NAS message. In a preferred example, the third NAS message may be a registration accept message, that is, the second indication information may be carried by the registration accept message.
[0130] For example, after the first network device receives the first indication information sent by the terminal device, the first network device may determine that there is a second network device and / or a third network device on the core network side that can process the first identifier, and then send a second indication information to the terminal device. The aforementioned way in which the first network device determines the second network device and / or the third network device may refer to that the first network device may select a second candidate network device and a third candidate network device from one or more candidate network devices; the first network device may determine whether the selected second candidate network device and the third candidate network device both support processing the first identifier, and if so, the first network device sends a second indication information to the terminal device. In this case, the second indication information may be used to indicate at least one of the following: the core network side supports processing the first identifier, and the core network side can recognize the first identifier.
[0131] It should be noted that if the first indication information is carried in the registration request message and the registration request message does not carry the first identifier, the first identifier can be carried by any one of the registration update message, the session establishment request message, and the session modification request message. That is, during the registration process after the terminal device is turned on, the terminal device sends the first indication information to the core network side to indicate that it has the ability to process the first identifier, and the core network side can also feedback the second indication information to the terminal device to indicate that it supports or can recognize the first identifier; after the terminal device obtains the second indication information, the terminal device can report the first identifier in other processing processes, for example, the first identifier can be carried in the registration update message in the registration update process, and / or the first identifier can be carried in the session establishment request message in the session establishment process, and / or the first identifier can be carried in the session modification request message in the session modification process.
[0132] Optionally, the first indication information may be sent together with the first identifier, that is, the registration request message may carry the first indication information and the first identifier.
[0133] In this case, the first network device may perform the aforementioned various processes after receiving the first identifier, which will not be repeated here.
[0134] In this case, the first network device may or may not send the second indication information. If the first network device sends the second indication information, the second indication information may be sent after the first network device obtains the configuration information associated with the first identifier; or the second indication information may be sent after the first network device determines that the second network device and / or the third network device on the core network side are capable of processing the first identifier. This does not limit all possible sending times of the second indication information.
[0135] In some possible implementations, the aforementioned terminal device does not send the first indication information but receives the second indication information. Correspondingly, the first network device does not receive the first indication information but sends the second indication information.
[0136] In this embodiment, the second indication information may be carried by a registration acceptance message. This embodiment may be applied to a situation where, after a terminal device sends a registration request message, the first network device may proactively send the second indication information to the terminal device if the first network device determines that a second network device and / or a third network device exists on the network side that can process the first identifier. In this case, the second indication information may be used to instruct the network side to request the terminal device to report the first identifier, wherein the network side may specifically be the core network side.
[0137] Furthermore, the terminal device may send the first identifier after receiving the second indication information. In this case, the first identifier may be carried by any one of a registration update message, a session establishment request message, and a session modification request message.
[0138] In the aforementioned implementation method in which the first identifier is carried by a registration request message and / or a registration update message, and in the implementation method in which the terminal device sends a first indication message to the first network device and / or receives a second indication message, the first network device may be an AMF; the second network device may be a PCF; and the third network device may be an UDM. It should be understood that the specific network elements of the above-mentioned first network device, second network device, and third network device are merely exemplary. In actual processing, they may be replaced with other possible core network network elements. It is also possible that the functions of the first network device, the second network device, and / or the third network device are merged into the same core network network element, that is, the first network device does not need to interact with other core network network elements to obtain the configuration information associated with the first identifier. All possible examples are not enumerated here. As long as the first network device, the second network device, and the third network device can implement the aforementioned functions, they are within the protection scope of this embodiment.
[0139] In conjunction with Figure 7, taking the terminal device as UE, the first network device as AMF, the second network device as PCF, and the third network device as UDM as an example, the processing of the first identifier carried by the registration request message in the above embodiment is exemplified. In the example of Figure 7, the first indication information is referred to as the first indication, that is, Figure 7 provides a registration process based on the "first indication" and / or "first identifier". When the UE initiates a registration process to the network for the first time, the main purpose of the UE sending the first indication and / or the first identifier (such as the user identifier) to the AMF in the registration process is to obtain the UE policy and access and mobility management-related subscription information corresponding to the user identifier. The UE can report the first indication and / or the first identifier during the initial registration process when it is turned on, and can also report the first indication / first identifier after the subsequent initial registration is completed (such as when the user using the UE changes).
[0140] Step 701: The UE adds a first indication and / or a first identity in a registration request, where the first indication is used to indicate that the UE supports reporting of the first identity. The first identity in this step refers to the first identity of the UE.
[0141] In step 701, the UE can still report the existing UE ID (such as SUPI or IMSI) and network slice identifier (S-NSSAI) for obtaining UE policy information and subscription information under the existing mechanism. In addition, in step 701, only the first indication can be sent. When the registration reply message confirms that the network supports or allows the ability to process the first identifier (that is, obtains the second indication information, or simply referred to as the second indication), the UE can report the first identifier in the subsequent registration process (or registration update process) and PDU session establishment / update process.
[0142] The AMF may then execute steps 702 to 704, as detailed below:
[0143] The processing of step 702 may include: the AMF determines the PCF and UDM to be interacted with based on the first indication and / or the first identifier. That is, after receiving the first indication and / or the first identifier of step 701, the AMF selects the PCF and / or UDM based on the first indication and / or the first identifier.
[0144] If the "first identifier" is not carried in step 701 and only the "first indication" is carried, after step 702 is completed, the UDM only needs to send the relevant information of "whether to support processing of the first identifier" to the AMF, and the AMF generates the second indication of step 705 accordingly, and then executes step 705.
[0145] If the "first identifier" is carried in step 701, the AMF determines the PCF and / or UDM that needs to interact according to the "first identifier" (or the first identifier and the first indication of the UE) in step 702; in step 703a, the AMF sends the first identifier (and / or the first indication) of the UE to the PCF, and the first identifier and / or the first indication of the UE may be carried by the PCF association establishment / modification (association est. / mod.) message shown in Figure 7; the PCF may trigger the UCU process to send the corresponding UE policy to the UE according to the first identifier of the UE; in step 703b, the AMF sends the first identifier of the UE (or the first identifier and the first indication of the UE) to the UDM, as shown in Figure 7, the first identifier and / or the first indication may be carried by the user subscription data acquisition service message (Nudm_SDM (subscriber data ma nagement)_Get(get)); in step 704, the UDM can reply to the corresponding access and mobility management contract information to the AMF. As shown in Figure 7, the response message (Nudm_SDM_Get_response(response)) of the user contract data acquisition service message can carry the corresponding mobility management (MM, Mobility Management) contract information (for the sake of simplicity in Figure 7, only the MM contract information is illustrated. In fact, the Nudm_SDM_Get_response can carry the access and mobility management contract information).
[0146] It should be noted that the UE policy is configured to the UE by the PCF through another separate process (UE Configuration Update) and is not reflected in the registration process signaling. In addition, the UE policy or subscription information sent by the PCF or UDM may refer to the content corresponding to the current "first identifier" value (that is, the UE policy associated with the UE's first identifier, or the subscription information associated with the UE's first identifier), or the PCF or UDM may also send an association relationship (such as sending the aforementioned first association relationship, second association relationship, etc., which has been described in detail in the aforementioned embodiment and will not be repeated here).
[0147] In addition, the above steps 703a and 703b may be performed in any order. Step 704 is performed after step 703b, that is, after step 703a is completed, step 704 may not be performed.
[0148] Step 705: The AMF carries a second indication in the registration reply message, where the second indication is used to indicate that the UE network side supports identifying the first identifier and / or supports the network supporting (or allowing or requiring) the UE to report the first identifier. The registration reply message may also be a Registration Accept message as shown in Figure 7. Step 705 may be performed directly after step 702, or after step 703a and / or step 704, and is not limited here.
[0149] It should be noted that Figure 7 also illustrates other network devices, such as the SMF and RAN. The SMF is a core network device and is shown in Figure 7 for the sake of architectural integrity. The role of the SMF in the example of Figure 7 is not limited here. The RAN can be an access network device serving the UE, and its role in the example of Figure 7 is also not limited.
[0150] In conjunction with Figure 8, taking the terminal device as UE, the first network device as AMF, the second network device as PCF, and the third network device as UDM as an example, the processing of the first identifier carried by the registration update message in the aforementioned embodiment is exemplified. The example in Figure 8 is mainly based on the registration process (or called the registration update process) of the updated "first identifier" value. When the terminal does not carry the "first identifier" during the initial registration process (that is, the registration request message in the example of Figure 7 only carries the "first indication"), or the user using the UE or the application service running on the UE changes (that is, the first identifier of the UE changes), the UE executes the registration process (not the first time) to replace the service with one or more core network elements (such as PCF) of the UE, and can obtain access and mobility management contract information and UE policy updates.
[0151] Step 801: The UE sends the (updated) value of the "first identity" (i.e., the UE's first identity or the updated UE's first identity) in the registration request. If the first identity (the value of the first identity, i.e., the UE's first identity) has been updated (not for the first time), the AMF may reselect the PCF and / or UDM network element based on this. The registration request in this step may be a registration update message.
[0152] It should be noted that if the first identifier of the UE is not carried together with the first indication in the example of Figure 7, this registration request carries the first identifier of the UE for the first time, otherwise it is an updated first identifier (that is, the updated value of the first identifier of the UE).
[0153] Steps 802-804: The (updated) first identifier (i.e., the UE's first identifier or the updated UE's first identifier) is sent to the PCF and / or UDM, which allows the PCF and / or UDM to determine whether the value of the first identifier has changed. If the PCF or UDM does not provide an "association relationship" in the example of Figure 7 , then in this process, the content corresponding to the updated first identifier value is sent to the peer end.
[0154] For example, in the processing of step 802, it may include: the AMF determines the PCF and UDM that need to interact according to the first identifier (that is, the first identifier of the UE or the updated first identifier of the UE). In step 803a, the AMF sends the first identifier of the UE to the PCF. For example, as shown in Figure 8, the PCF association establishment / modification (association est. / mod.) message carries the updated first identifier (i.e., the updated first identifier of the UE) and is sent to the PCF. Subsequently, the PCF can trigger the UCU process according to the first identifier of the UE to send the corresponding UE policy to the UE; in step 803b, the AMF sends the first identifier to the UDM. As shown in Figure 8, the updated first identifier (i.e., the updated first identifier of the UE) can be carried by the user subscription data acquisition service message (Nudm_SDM_Get) message; in step 804, the UDM can reply to the AMF with its corresponding access and mobility management subscription information. As shown in Figure 8, the response message (Nudm_SDM_Get_response) of the user subscription data acquisition service message can carry the corresponding mobility management (MM) subscription information (for simplicity, only the MM subscription information is illustrated in Figure 8. In fact, the Nudm_SDM_Get_response can carry access and mobility management subscription information).
[0155] It should also be noted that if in the example of Figure 7, the AMF has obtained the aforementioned second association relationship, the AMF can directly select the subscription information associated with the updated first identifier and send it to the UE.
[0156] Step 805: The AMF sends a registration reply message to the UE. The registration reply message may also be a registration accept message as shown in FIG8 . It should be noted that FIG8 also illustrates other network devices, such as the SMF and RAN. The SMF is a device on the core network side and is shown in FIG8 for completeness. The roles of the SMF and the RAN are also not limited.
[0157] In some possible implementations, the first identifier may be carried by a session establishment request message and / or a session modification request message.
[0158] It should be noted that, in addition to carrying the first identifier, the session establishment request and / or session modification request message may also carry other information specified by relevant protocols, but this embodiment does not list all of them.
[0159] It should also be noted that the session establishment request may be the first time that the first identifier is carried, or the session establishment request may be the second time that the first identifier is carried in the registration request message and / or the registration update message. For example, after the first identifier is carried in the registration request message, if the first identifier is carried again in the session establishment request, the value of the first identifier carried in the registration request message may be different from the value of the first identifier carried in the session establishment request. Similarly, the session modification request message may be the first time that the first identifier is carried, or the session modification request message may be the second time that the first identifier is carried in the registration request message and / or the registration update message and / or the session establishment request message. For example, after the first identifier is carried in the session establishment request message, if the first identifier is carried again in the session modification request message, the value of the first identifier carried in the session modification request message may be different from the value of the first identifier carried in the session establishment request message.
[0160] After the first network device receives the first identifier, the method also includes at least one of the following: the first network device obtains the policy rules associated with the first identifier from the second network device; the first network device obtains the contract information associated with the first identifier from the third network device; the first network device determines the contract information associated with the first identifier based on the second association relationship; the first network device determines the policy rules associated with the first identifier based on the third association relationship.
[0161] Unlike the previous embodiment, in this embodiment, the first network device may not directly receive the first identifier sent by the terminal device. Instead, the first network device may receive the first identifier sent by the terminal device through a fifth network device. In other words, the fifth network device can be used to interact directly with the terminal device. Furthermore, the fifth network device is used to forward the session establishment request message, and the function of the first network device may be to establish a context. The first network device may be selected by the fifth network device, for example, a first network device that the fifth network device can support or recognize the value of the first identifier.
[0162] In some possible examples, the first network device obtains the policy rules associated with the first identifier from the second network device, including: the first network device sends the first identifier to the second network device, and receives the policy rules associated with the first identifier sent by the second network device.
[0163] For example, after receiving the first identifier, the first network device can send the first identifier to the second network device. The second network device can determine the policy rules associated with the first identifier based on the third association relationship, and the second network device sends the policy rules associated with the first identifier to the first network device.
[0164] In some possible examples, the first network device determines the policy rule associated with the first identifier based on the third association relationship.
[0165] If this is the first time the first network device is performing processing based on the first identifier, the first network device may send the first identifier to the second network device and receive the third association relationship and / or the first association relationship from the second network device. The first network device may then determine the policy rule associated with the first identifier based on the received third association relationship. For example, if the first identifier is carried in a session establishment request and this is the first time the first network device has received the first identifier, the first network device may perform the above processing.
[0166] If this is not the first time that the first network device performs processing based on the first identifier, the first network device may have already saved the third association relationship. The first network device may first detect whether it has saved the third association relationship. If so, it may directly determine the policy rules associated with the first identifier based on the third association relationship. If not, the first network device may send the first identifier to the second network device and receive the third association relationship sent by the second network device. The first network device may determine the policy rules associated with the first identifier based on the received third association relationship. For example, if the last first identifier is carried by the session establishment request, and the last first identifier is the first identifier received by the first network device for the first time, the first network device may obtain the third association relationship. If the first identifier is received again by the session modification request message this time, the first network device may directly determine the policy rules associated with the first identifier based on the saved third association relationship.
[0167] In some possible examples, the first network device obtains the contract information associated with the first identifier from the third network device, including: the first network device sends the first identifier to the third network device, and receives the contract information associated with the first identifier sent by the third network device.
[0168] For example, after receiving the first identifier, the first network device can send the first identifier to the third network device. The third network device can determine the contract information associated with the first identifier based on the second association relationship, and the third network device sends the contract information associated with the first identifier to the first network device.
[0169] In some possible examples, the first network device determines the subscription information associated with the first identifier based on the second association relationship.
[0170] If the first network device is processing based on the first identifier for the first time, the first network device may send the first identifier to the second network device, which may then send the first identifier to the third network device and receive the second association relationship from the third network device. The first network device may then determine the contract information associated with the first identifier based on the received second association relationship.
[0171] If this is not the first time that the first network device performs processing based on the first identifier, the first network device may have already saved the second association relationship. The first network device may first detect whether it has saved the second association relationship. If so, the first network device may directly determine the contract information associated with the first identifier based on the second association relationship. If not, the first network device may send the first identifier to the third network device and receive the second association relationship sent by the third network device. The first network device may determine the contract information associated with the first identifier based on the received second association relationship.
[0172] It should also be pointed out that in this embodiment, the contract information associated with the first identifier may at least include the session management contract (or session management contract information) associated with the first identifier.
[0173] Furthermore, in the processing of the first network device, the method also includes at least one of the following: the first network device determines the quality of service QoS rules associated with the first identifier based on the contract information associated with the first identifier and / or the policy rules associated with the first identifier; the first network device determines the QoS parameters associated with the first identifier based on the contract information associated with the first identifier and / or the policy rules associated with the first identifier; the first network device determines the data packet detection rules PDR associated with the first identifier based on the contract information associated with the first identifier and / or the policy rules associated with the first identifier.
[0174] The method further includes at least one of the following: the first network device sends the quality of service (QoS) rules associated with the first identifier to the terminal device; the first network device sends the QoS parameters associated with the first identifier to the access network device, wherein the access network device serves the terminal device; the first network device sends the PDR associated with the first identifier to the fourth network device. Here, the access network device serving the terminal device may be a fourth access network device, that is, the fourth access network device serves the terminal device. The fourth access network device may be the same as or different from the aforementioned first access network device, second access network device, and third access network device, and this embodiment does not limit this.
[0175] Correspondingly, after the terminal device sends the first identifier, the method also includes: the terminal device receives the quality of service QoS rules associated with the first identifier, wherein the QoS rules associated with the first identifier are determined based on the contract information associated with the first identifier and / or the policy rules associated with the first identifier.
[0176] In this embodiment, the specific processing of determining at least one of the QoS rules, QoS parameters, and PDRs associated with the first identifier by the first network device is not limited here. It should be noted that at least one of the QoS rules, PDRs, and QOS parameters can be used to achieve at least one of the following: controlling the type of transmitted data, controlling the content of accessible applications, controlling the type of accessible data, adjusting or controlling the transmission quality of business data, and so on. In the solution provided by this embodiment, as the value of the first identifier is different, different QoS rules, different QoS parameters, and at least one of different PDRs can be determined. In this way, the same terminal device can achieve the effect of more accurately controlling the type of transmitted data, and / or controlling the content of accessible applications, and / or controlling the type of accessible data, and / or adjusting or controlling the transmission quality of business data as at least one of the users, services, and applications is different. Taking the example of different values of the first identifier used to indicate different users using the terminal device, as different users use the same terminal device, due to the different values of the first identifier, at least one of the QoS rule associated with the first identifier and the PDR associated with the first identifier will be different, so that different users can access different applications when using the terminal device. For example, when a child logs into the terminal device, it is necessary to limit access to only content suitable for children (such as websites and / or applications suitable for children). Using the solution provided by this embodiment, the QoS rule associated with the first identifier (that is, used to indicate that a child is using the terminal device) and the PDR associated with the first identifier can be used to control which types of data streams can be transmitted, thereby achieving the above-mentioned effect. For another example, after different users log into the same terminal device, they have different requirements for service bandwidth. Some users may have activated high-definition video services. In this case, after these users log in to the terminal device, the network needs to provide them with higher QoS parameters to enable the transmission of high-definition service data.
[0177] The first network device sends the QoS parameters associated with the first identifier to the access network device, which can be: the first network device sends the QoS parameters associated with the first identifier to the access network device through the fifth network device; or, the first network device directly sends the QoS parameters associated with the first identifier to the access network device.
[0178] The first network device sends the PDR associated with the first identifier to the fourth network device. The first network device may send the PDR associated with the first identifier to the fourth network device through the fifth network device; or the first network device may directly send the PDR associated with the first identifier to the fourth network device.
[0179] The first network device may send the quality of service (QoS) rule associated with the first identifier to the terminal device in a manner such that: the first network device sends the quality of service (QoS) rule associated with the first identifier to the terminal device via a fifth network device. Furthermore, the first network device may send the quality of service (QoS) rule associated with the first identifier to the terminal device via the fifth network device in a manner such that: the first network device sends the quality of service (QoS) rule associated with the first identifier to the terminal device via the fifth network device and an access network device, and the access network device serves the terminal device.
[0180] In the aforementioned implementation where the first identifier is carried by a session establishment request message and / or a session modification request message, the first network device may be an SMF, the second network device may be a PCF, and the third network device may be an UDM. It should also be understood that the specific network elements of the aforementioned first, second, and third network devices are merely illustrative. In actual processing, as long as the network devices can implement the aforementioned functions, they are within the scope of protection of this embodiment, and this does not exhaustively enumerate all possible network devices. Furthermore, the aforementioned fourth network device may be a UPF, and the aforementioned fifth network device may be an AMF.
[0181] In conjunction with Figure 9, taking the terminal device as UE, the first network device as SMF, the second network device as PCF, the third network device as UDM, the fourth network device as UPF, and the fifth network device as AMF as an example, the processing of the first identifier carried by the session establishment request message in the aforementioned embodiment is exemplified. The example in Figure 9 is a process for establishing a PDU session based on the "first identifier". In the PDU session establishment process, it is necessary to consider who the specific user using the UE is, that is, the value of the "first identifier". By reporting the first identifier by the UE, the core network element (such as SMF) can obtain the corresponding subscription information and policy information, thereby establishing a QoS flow of specific QoS parameters and binding rules for the QoS flow.
[0182] Step 901: The UE carries its first identifier in a PDU session establishment request message, and the AMF determines the selection of an SMF based on the first identifier of the UE. The PDU session establishment request message may be the session establishment request message in the aforementioned embodiment.
[0183] The processing of steps 902-904 includes:
[0184] Step 902: The AMF sends the PDU session establishment request information and the first identifier to the SMF via an N11 interface message. As shown in Figure 9, in step 902, the first identifier may be carried by the Nsmf_PDU Session_CreateSMContext Request message.
[0185] Then, the SMF interacts with the UDM and / or PCF according to the first identifier. The interaction includes:
[0186] Step 903 and step 904: SMF selects UDM and / or PCF to interact based on the first identifier; during the interaction process, SMF carries the first identifier to inform UDM and / or PCF to obtain the contract information and / or policy information corresponding to the first identifier. In Figure 9, the interaction process between SMF and UDM is represented as step 903, and the interaction process between SMF and PCF is represented as step 904. In actual processing, steps 903 and 904 can be performed in any order. In Figure 9, the process used in the interaction process between SMF and UDM in step 903 is illustrated as a Subscription retrieval / updates process. The first identifier is carried in any signaling sent by SMF to UDM in the Subscription retrieval / updates process. In FIG9 , the process used in the interaction process between the SMF and the PCF in step 904 is illustrated as a Policy Association Establishment process, and any signaling sent from the SMF to the PCF in the Policy Association Establishment process carries the first identifier.
[0187] Here, the contract information and / or policy information sent by UDM and PCF can be the contract information and / or policy information corresponding to the first identifier of the UE; or the contract information and / or policy information sent by UDM and PCF can be a list of information corresponding to different values of the first identifier, that is, the aforementioned third association relationship and second association relationship, so that when the first identifier (value) of the subsequent UE changes, after the UE modifies and reports the updated first identifier (value) through the PDU session, the SMF can directly find the corresponding new contract information and / or policy information parameters based on the aforementioned third association relationship and second association relationship. Each second identifier in the second association relationship is called the second identifier value (that is, various values of the first type of identifier), and the contract information in the second association relationship is called the contract information parameter value, then the second association relationship can be as shown in Table 1:
[0188] Table 1
[0189] It can be seen from Table 1 that when the second identifier value is 1, the contract information (i.e., contract information parameter) -1 is associated, and when the second identifier value is 2, the contract information -2 (i.e., contract information parameter -2) is associated. No further details are given.
[0190] Each second identifier in the third association relationship is referred to as a second identifier value (i.e., various values of the first type of identifier), and the policy rule in the third association relationship is referred to as a policy information parameter value. The third association relationship may be as shown in Table 2:
[0191] Table 2
[0192] It can be seen from Table 2 that when the second identifier value is 1, the associated policy information (ie, policy information parameter) -1 is associated, and when the second identifier value is 2, the associated policy information -2 (ie, policy information parameter -2) is associated, which will not be detailed one by one.
[0193] Steps 905-907: The SMF determines the PCC rules based on the subscription information and / or policy information obtained, and generates QoS rules, PDR rules, and QoS parameters corresponding to the QoS flow. These are then sent to the corresponding UE, RAN, and UPF for execution.
[0194] Specifically, in step 905, the SMF determines the QoS rules, PDR rules, and QoS parameters based on the subscription information and / or policy information obtained by the first identifier. For example, the SMF determines the PCC rules based on the subscription information and / or policy information obtained by the first identifier, and generates the QoS rules, PDR rules, and QoS parameters corresponding to the QoS flow.
[0195] In step 906, the SMF sends an N1, N2 interface communication message transfer message (Namf-communication-N1N2MessageTransfer) to the AMF. Specifically, the Namf-communication-N1N2MessageTransfer may carry QoS rules, PDRs, and QoS parameters (that is, the QoS rules, PDRs, and QoS parameters associated with the first identifier).
[0196] In step 907, the AMF sends the QoS parameters (that is, the QoS parameters associated with the first identity of the UE) to the RAN through an N2 message (which may carry a NAS message and QoS parameters, etc.).
[0197] In step 908, the RAN establishes AN resources and forwards the NAS message to the UE. The NAS message in steps 907 and 908 may carry QoS rules (ie, QoS rules associated with the first identifier of the UE).
[0198] In addition, step 909 may be included, where the AMF may send the PDR to the UPF. Step 909 and step 907 may be in any order.
[0199] In conjunction with Figure 10, taking the terminal device as UE, the first network device as SMF, the second network device as PCF, the third network device as UDM, the fourth network device as UPF, and the fifth network device as AMF as an example, the processing of the first identifier carried by the session establishment request message in the above embodiment is exemplified. The example of Figure 10 is based on the PDU session modification of the "first identifier". The modification of the PDU session can be used when the user using the UE changes or the application service running on the UE changes, that is, the corresponding "first identifier" value also changes. At this time, the PDU session modification process can be used to modify the relevant parameters. Due to the change of the user, it may be necessary to reselect the SMF and re-interact with the UDM and PCF to obtain new contract information and policy information. If the policy information or contract information corresponding to different first identifier values has been obtained during the PDU session establishment process, there is no need to interact with the UDM and PCF.
[0200] Step 1001: When the user using the same UE changes or the first identifier (i.e., the value of the first identifier) changes due to other reasons, the UE may send a PDU Session Modification request to the AMF. At this time, the AMF may reselect the SMF based on the updated first identifier (i.e., the updated first identifier) (this reselection action is not supported in the existing process);
[0201] Step 1002: The request message sent by the AMF to the SMF carries the updated first identifier. The request message may specifically be the Nsmf_PDUSession_UpdateSMContext Request shown in FIG10 .
[0202] Steps 1003-1004 (optional): The SMF uses the updated first identifier to determine whether the PCF and / or UDM needs to be replaced, and interacts with the PCF and UDM to obtain new policy information and / or subscription information (i.e., the policy information and / or subscription information associated with the updated UE's first identifier). If, in Figure 9, the UDM and PCF send Table 1 or Table 2 to the SMF, steps 1003-1004 can be skipped. The specific description of steps 1003 and 1004 is the same as steps 903 and 904 in the aforementioned example and will not be repeated.
[0203] Steps 1005 to 1009: The SMF determines the QoS parameters, QoS rules, and PDR (that is, the QoS rules, PDR, and QoS parameters associated with the UE's first identifier) based on the updated subscription information and policy information obtained by the updated first identifier, and sends them to the corresponding UE, RAN, and UPF for execution. Specifically, the SMF determines the PCC rules based on the updated subscription information and / or policy information, generates the QoS rules, PDR rules, and QoS parameters corresponding to the QoS flow, and sends them to the corresponding UE, RAN, and UPF for execution.
[0204] Steps 1005-1009 are the same as the specific descriptions of steps 905 to 909 in FIG9 , and are not repeated here.
[0205] It can be seen that by adopting the solution provided by the above embodiment, the terminal device can send a first identifier, which is used to indicate information related to the terminal device. The information related to the terminal device may include at least one of information about the user using the terminal device, information about the application and / or service running on the terminal device, etc., so that the configuration information associated with it can be obtained based on the first identifier. In this way, the network side can determine the configuration information associated with the terminal device based on the information related to the user and / or service and / or application of the terminal device, avoiding the problem in the related art that the configuration information can only be determined for the terminal device based on the ID of the terminal device, and the configuration information cannot be flexibly adjusted in combination with different users and / or different applications and / or different services.
[0206] FIG11 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application, including:
[0207] The first communication unit 1101 is used to send a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about the user using the terminal device, information about the application running on the terminal device, and information about the service running on the terminal device. The first identifier is used to determine the configuration information associated with the first identifier.
[0208] The information of the user using the terminal device includes at least one of the following: an identification of the user using the terminal device, and biometric information of the user using the terminal device.
[0209] The configuration information associated with the first identifier includes at least one of the following: the UE policy associated with the first identifier; the subscription information associated with the first identifier; the policy rules associated with the first identifier; and one or more electronic devices associated with the first identifier.
[0210] The terminal device shown in FIG11 further includes: a first processing unit 1102;
[0211] The first processing unit 1102 is configured to determine a UE policy associated with the first identifier based on a first association relationship, wherein the first association relationship includes a UE policy associated with each of the one or more second identifiers;
[0212] Alternatively, the first communication unit is configured to receive a UE policy associated with the first identifier after sending the first identifier.
[0213] The first communication unit is configured to receive the first association relationship.
[0214] The first communication unit is used to receive the quality of service QoS rules associated with the first identifier, wherein the QoS rules associated with the first identifier are determined based on the contract information associated with the first identifier and / or the policy rules associated with the first identifier.
[0215] The first identifier is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.
[0216] The first communication unit is used to send first indication information, wherein the first indication information is used to indicate at least one of the following: the terminal device supports reporting the first identifier, the terminal device can recognize the first identifier, and the terminal device can process the first identifier.
[0217] The first communication unit is used to receive second indication information, wherein the second indication information is used to indicate at least one of the following: the network side supports processing the first identifier, the network side can identify the first identifier, the network side requests the terminal device to report the first identifier, the network side requires the terminal device to report the first identifier, and the network side allows the terminal device to report the first identifier.
[0218] The first indication information is carried by the registration request message.
[0219] The second indication information is carried by the registration accept message.
[0220] FIG12 is a schematic diagram of the composition structure of a first network device according to an embodiment of the present application, including:
[0221] The second communication unit 1201 is used to receive a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about the user using the terminal device, information about the application running on the terminal device, and information about the service running on the terminal device. The first identifier is used to determine the configuration information associated with the first identifier.
[0222] The information of the user using the terminal device includes at least one of the following: an identification of the user using the terminal device, and biometric information of the user using the terminal device.
[0223] The configuration information associated with the first identifier includes at least one of the following: the UE policy associated with the first identifier; the subscription information associated with the first identifier; the policy rules associated with the first identifier; and other terminals associated with the first identifier.
[0224] FIG12 is a schematic diagram of the composition structure of the first network device, further comprising: a second processing unit 1202;
[0225] The second processing unit 1202 is configured to perform at least one of the following: determining, based on the second association relationship, subscription information associated with the first identifier, wherein the second association relationship includes subscription information associated with each of the one or more second identifiers; determining, based on the third association relationship, a policy rule associated with the first identifier, wherein the third association relationship includes a policy rule associated with each of the one or more second identifiers; and determining, based on the first association relationship, a UE policy associated with the first identifier, wherein the first association relationship includes a UE policy associated with each of the one or more second identifiers.
[0226] Or / and, the second communication unit is used to perform at least one of the following: sending the first identifier to the second network device, the first identifier is used by the second network device to determine the UE policy associated with the first identifier; obtaining the policy rules associated with the first identifier from the second network device; obtaining the subscription information associated with the first identifier from the third network device; obtaining the UE policy associated with the first identifier from the second network device.
[0227] The second communication unit is configured to send the first identifier to the second network device and receive the policy rules associated with the first identifier sent by the second network device.
[0228] The second communication unit is configured to send the first identifier to the third network device and receive contract information associated with the first identifier sent by the third network device.
[0229] The second communication unit is used to perform at least one of the following: sending the first identifier to the third network device and receiving the second association relationship sent by the third network device; sending the first identifier to the second network device and receiving the third association relationship and / or the first association relationship sent by the second network device.
[0230] The second processing unit is used to perform at least one of the following: determining the quality of service QoS rules associated with the first identifier based on the contract information associated with the first identifier and / or the policy rules associated with the first identifier; determining the QoS parameters associated with the first identifier based on the contract information associated with the first identifier and / or the policy rules associated with the first identifier; determining the data packet detection rules PDR associated with the first identifier based on the contract information associated with the first identifier and / or the policy rules associated with the first identifier.
[0231] The second communication unit is used to perform at least one of the following: sending the quality of service QoS rules associated with the first identifier to the terminal device; sending the QoS parameters associated with the first identifier to the access network device, wherein the access network device serves the terminal device; sending the PDR associated with the first identifier to the fourth network device.
[0232] The second communication unit is used to perform one of the following: sending the UE policy associated with the first identifier to the terminal device; sending the first association relationship to the terminal device.
[0233] The first identifier is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.
[0234] The second communication unit is used to receive the first indication information sent by the terminal device, wherein the first indication information is used to indicate at least one of the following: the terminal device supports reporting the first identifier, the terminal device can recognize the first identifier, and the terminal device can process the first identifier.
[0235] The second communication unit is used to send second indication information to the terminal device, wherein the second indication information is used to indicate at least one of the following: the network side supports processing the first identifier, the network side can identify the first identifier, the network side requests the terminal device to report the first identifier, the network side requires the terminal device to report the first identifier, and the network side allows the terminal device to report the first identifier.
[0236] The first indication information is carried by the registration request message.
[0237] The second indication information is carried by the registration accept message.
[0238] The fourth network device is a user plane function UPF.
[0239] The second network device is a policy control function PCF; the third network device is a unified data management function UDM.
[0240] The first network device is an access and mobility management function AMF or a session management function SMF.
[0241] The device of the embodiment of the present application can realize the corresponding functions of each device in the aforementioned communication method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the terminal device or each module (sub-module, unit or component, etc.) in the first network device can be found in the corresponding description in the above method embodiment, which will not be repeated here. It should be noted that the functions described in the terminal device of the embodiment of the application or each module (sub-module, unit or component, etc.) in the first network device can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.).
[0242] Figure 13 is a schematic diagram of a communication device 1300 according to an embodiment of the present application. The communication device 1300 includes a processor 1310, which can retrieve and execute computer programs from a memory to enable the communication device 1300 to implement the methods according to the embodiments of the present application. In one possible implementation, the communication device 1300 may also include a memory 1320. The processor 1310 can retrieve and execute computer programs from the memory 1320 to enable the communication device 1300 to implement the methods according to the embodiments of the present application. The memory 1320 may be a separate device independent of the processor 1310 or integrated into the processor 1310. In one possible implementation, the communication device 1300 may also include a transceiver 1330. The processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, the transceiver 1330 may send information or data to other devices or receive information or data sent by other devices. The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include one or more antennas.
[0243] In one possible implementation, the communication device 1300 may be a terminal device according to an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the terminal device in each method according to the embodiment of the present application. For the sake of brevity, detailed description is omitted here. In one possible implementation, the communication device 1300 may be a first network device according to an embodiment of the present application, and the communication device 1300 may implement the corresponding processes implemented by the first network device in each method according to the embodiment of the present application. For the sake of brevity, detailed description is omitted here.
[0244] Figure 14 is a schematic structural diagram of a chip 1400 according to an embodiment of the present application. The chip 1400 includes a processor 1410, which can call and run a computer program from a memory to implement the method in the embodiment of the present application. In one possible implementation, the chip 1400 may also include a memory 1420. The processor 1410 can call and run a computer program from the memory 1420 to implement the method performed by the first device or the target second device in the embodiment of the present application. The memory 1420 can be a separate device independent of the processor 1410, or it can be integrated into the processor 1410. In one possible implementation, the chip 1400 may also include an input interface 1430. The processor 1410 can control the input interface 1430 to communicate with other devices or chips, specifically, to obtain information or data sent by other devices or chips. In one possible implementation, the chip 1900 may also include an output interface 1440. The processor 1410 may control the output interface 1440 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0245] In one possible implementation, the chip can be applied to the terminal device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal device in the various methods of the embodiment of the present application. For the sake of brevity, it is not repeated here. In one possible implementation, the chip can be applied to the first network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first network device in the various methods of the embodiment of the present application. For the sake of brevity, it is not repeated here. It should be understood that the chip mentioned in the embodiment of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc. The processor mentioned above can be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC) or other programmable logic device, transistor logic device, discrete hardware component, etc. Among them, the general-purpose processor mentioned above can be a microprocessor or any conventional processor, etc. The memory mentioned above can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memory. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory. The volatile memory can be a random access memory (RAM). It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiment of the present application can also be a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DR RAM), etc. That is, the memory in the embodiment of the present application is intended to include but is not limited to these and any other suitable types of memory.
[0246] Figure 15 is a schematic block diagram of a communication system 1500 according to an embodiment of the present application. Communication system 1500 includes a terminal device 1510 and a first network device 1520. Terminal device 1510 can be used to implement the corresponding functions implemented by the terminal device in the above-described method. First network device 1520 can be used to implement the corresponding functions implemented by the first network device in the above-described method. For the sake of brevity, these details are not further described here.
[0247] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).
[0248] It should be understood that in the various embodiments of the present application, the size of the sequence number of each process mentioned above does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application. Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. The above is only a specific implementation method of the present application, but the scope of protection of the present application is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the present application, which should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claim.
Claims
1. A communication method, include: The terminal device sends a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about a user using the terminal device, information about an application running on the terminal device, and information about a service running on the terminal device, and the first identifier is used to determine configuration information associated with the first identifier.
2. The method according to claim 1, in, The information of the user using the terminal device includes at least one of the following: an identification of the user using the terminal device, and biometric information of the user using the terminal device.
3. The method according to claim 1 or 2, in, The configuration information associated with the first identifier includes at least one of the following: a UE policy associated with the first identifier; The contract information associated with the first identifier; a policy rule associated with the first identifier; One or more electronic devices associated with the first identification.
4. The method according to any one of claims 1 to 3, in, After the terminal device sends the first identifier, the method further includes one of the following: The terminal device receives a UE policy associated with the first identifier; The terminal device determines the UE policy associated with the first identifier based on the first association relationship, wherein the first association relationship includes the UE policy associated with each second identifier of one or more second identifiers.
5. The method according to claim 4, in, Before the terminal device determines, based on the first association relationship, a UE policy associated with the first identifier, the method further includes: The terminal device receives the first association relationship.
6. The method according to any one of claims 1 to 5, in, After the terminal device sends the first identifier, the method further includes: The terminal device receives the quality of service QoS rules associated with the first identifier, wherein the QoS rules associated with the first identifier are determined based on the subscription information associated with the first identifier and / or the policy rules associated with the first identifier.
7. The method according to any one of claims 1 to 6, in, The first identifier is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.
8. The method according to any one of claims 1 to 7, in, The method further comprises: The terminal device sends first indication information, wherein the first indication information is used to indicate at least one of the following: the terminal device supports reporting of the first identifier, the terminal device can recognize the first identifier, and the terminal device can process the first identifier.
9. The method according to any one of claims 1 to 8, in, The method further comprises: The terminal device receives second indication information, wherein the second indication information is used to indicate at least one of the following: the network side supports processing the first identifier, the network side can identify the first identifier, the network side requests the terminal device to report the first identifier, the network side requires the terminal device to report the first identifier, and the network side allows the terminal device to report the first identifier.
10. The method according to claim 8, in, The first indication information is carried by the registration request message.
11. The method according to claim 9, in, The second indication information is carried by the registration acceptance message.
12. A communication method, include: A first network device receives a first identifier, wherein the first identifier is used to indicate information related to a terminal device, the information related to the terminal device including at least one of the following: information about a user using the terminal device, information about an application running on the terminal device, and information about a service running on the terminal device, and the first identifier is used to determine configuration information associated with the first identifier.
13. The method according to claim 12, in, The information of the user using the terminal device includes at least one of the following: an identification of the user using the terminal device, and biometric information of the user using the terminal device.
14. The method according to claim 12 or 13, in, The configuration information associated with the first identifier includes at least one of the following: a UE policy associated with the first identifier; The contract information associated with the first identifier; a policy rule associated with the first identifier; Other terminals associated with the first identifier.
15. The method according to any one of claims 12 to 14, in, After the first network device receives the first identifier, the method further includes at least one of the following: The first network device sends the first identifier to the second network device, where the first identifier is used by the second network device to determine a UE policy associated with the first identifier; The first network device obtains the policy rule associated with the first identifier from the second network device; The first network device obtains the contract information associated with the first identifier from the third network device; The first network device determines, based on a second association relationship, contract information associated with the first identifier, wherein the second association relationship includes contract information associated with each of the one or more second identifiers; The first network device determines the policy rule associated with the first identifier based on the third association relationship, wherein the third association relationship includes the policy rule associated with each second identifier in the one or more second identifiers; The first network device obtains, from the second network device, a UE policy associated with the first identifier; The first network device determines the UE policy associated with the first identifier based on a first association relationship, wherein the first association relationship includes the UE policy associated with each second identifier of the one or more second identifiers.
16. The method according to claim 15, in, The first network device obtains the policy rule associated with the first identifier from the second network device, including: The first network device sends the first identifier to the second network device, and receives the policy rule associated with the first identifier sent by the second network device.
17. The method according to claim 15, in, The first network device obtains the contract information associated with the first identifier from the third network device, including: The first network device sends the first identifier to the third network device, and receives the contract information associated with the first identifier sent by the third network device.
18. The method according to claim 15, in, The method further comprises at least one of the following: The first network device sends the first identifier to the third network device, and receives the second association relationship sent by the third network device; The first network device sends the first identifier to the second network device, and receives the third association relationship and / or the first association relationship sent by the second network device.
19. The method according to any one of claims 12 to 18, in, The method further comprises at least one of the following: The first network device determines a quality of service (QoS) rule associated with the first identifier based on the subscription information associated with the first identifier and / or the policy rule associated with the first identifier; The first network device determines the QoS parameter associated with the first identifier based on the subscription information associated with the first identifier and / or the policy rule associated with the first identifier; The first network device determines a data packet detection rule PDR associated with the first identifier based on the subscription information associated with the first identifier and / or the policy rule associated with the first identifier.
20. The method according to claim 19, in, The method further comprises at least one of the following: The first network device sends a quality of service (QoS) rule associated with the first identifier to the terminal device; The first network device sends the QoS parameter associated with the first identifier to an access network device, wherein the access network device serves the terminal device; The first network device sends the PDR associated with the first identifier to the fourth network device.
21. The method according to any one of claims 15 to 18, in, The method further comprises one of the following: The first network device sends a UE policy associated with the first identifier to the terminal device; The first network device sends the first association relationship to the terminal device.
22. The method according to any one of claims 12 to 21, in, The first identifier is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.
23. The method according to any one of claims 12 to 22, in, The method further comprises: The first network device receives first indication information sent by the terminal device, wherein the first indication information is used to indicate at least one of the following: the terminal device supports reporting of a first identifier, the terminal device can recognize the first identifier, and the terminal device can process the first identifier.
24. The method according to any one of claims 12 to 23, in, The method further comprises: The first network device sends second indication information to the terminal device, wherein the second indication information is used to indicate at least one of the following: the network side supports processing the first identifier, the network side can identify the first identifier, the network side requests the terminal device to report the first identifier, the network side requires the terminal device to report the first identifier, and the network side allows the terminal device to report the first identifier.
25. The method according to claim 23, in, The first indication information is carried by the registration request message.
26. The method according to claim 24, in, The second indication information is carried by the registration acceptance message.
27. The method according to claim 20, in, The fourth network device is a user plane function UPF.
28. The method according to any one of claims 15 to 21, in, The second network device is a policy control function PCF; the third network device is a unified data management function UDM.
29. The method according to any one of claims 12 to 28, in, The first network device is an access and mobility management function AMF or a session management function SMF.
30. A terminal device, include: A first communication unit is used to send a first identifier, wherein the first identifier is used to indicate information related to the terminal device, and the information related to the terminal device includes at least one of the following: information about a user using the terminal device, information about an application running on the terminal device, and information about a service running on the terminal device. The first identifier is used to determine configuration information associated with the first identifier.
31. The terminal device according to claim 30, in, The information of the user using the terminal device includes at least one of the following: an identification of the user using the terminal device, and biometric information of the user using the terminal device.
32. The terminal device according to claim 30 or 31, in, The configuration information associated with the first identifier includes at least one of the following: the UE policy associated with the first identifier; the contract information associated with the first identifier; the policy rule associated with the first identifier; and one or more electronic devices associated with the first identifier.
33. The terminal device according to any one of claims 30 to 32, in, Also included: a first processing unit; The first processing unit is configured to determine a UE policy associated with the first identifier based on a first association relationship, wherein the first association relationship includes a UE policy associated with each of the one or more second identifiers; Alternatively, the first communication unit is used to receive a UE policy associated with the first identifier after sending the first identifier.
34. The terminal device according to claim 33, in, The first communication unit is used to receive the first association relationship.
35. The terminal device according to any one of claims 30 to 34, in, The first communication unit is used to receive the quality of service QoS rules associated with the first identifier, wherein the QoS rules associated with the first identifier are determined based on the contract information associated with the first identifier and / or the policy rules associated with the first identifier.
36. The terminal device according to any one of claims 30 to 35, in, The first identifier is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.
37. The terminal device according to any one of claims 30 to 36, in, The first communication unit is used to send first indication information, wherein the first indication information is used to indicate at least one of the following: the terminal device supports reporting the first identifier, the terminal device can recognize the first identifier, and the terminal device can process the first identifier.
38. The terminal device according to any one of claims 30 to 37, in, The first communication unit is used to receive second indication information, wherein the second indication information is used to indicate at least one of the following: the network side supports processing the first identifier, the network side can identify the first identifier, the network side requests the terminal device to report the first identifier, the network side requires the terminal device to report the first identifier, and the network side allows the terminal device to report the first identifier.
39. The terminal device according to claim 37, in, The first indication information is carried by the registration request message.
40. The terminal device according to claim 38, in, The second indication information is carried by the registration acceptance message.
41. A first network device, include: A second communication unit is used to receive a first identifier, wherein the first identifier is used to indicate information related to a terminal device, and the information related to the terminal device includes at least one of the following: information about a user using the terminal device, information about an application running on the terminal device, and information about a service running on the terminal device, and the first identifier is used to determine configuration information associated with the first identifier.
42. The first network device according to claim 41, in, The information of the user using the terminal device includes at least one of the following: an identification of the user using the terminal device, and biometric information of the user using the terminal device.
43. The first network device according to claim 41 or 42, in, The configuration information associated with the first identifier includes at least one of the following: UE policy associated with the first identifier; subscription information associated with the first identifier; policy rules associated with the first identifier; other terminals associated with the first identifier.
44. The first network device according to any one of claims 41 to 43, in, Also includes: a second processing unit; The second processing unit is used to perform at least one of the following: based on the second association relationship, determine the contract information associated with the first identifier, wherein the second association relationship includes the contract information associated with each second identifier in the one or more second identifiers; based on the third association relationship, determine the policy rule associated with the first identifier, wherein the third association relationship includes the policy rule associated with each second identifier in the one or more second identifiers; based on the first association relationship, determine the UE policy associated with the first identifier, wherein the first association relationship includes the UE policy associated with each second identifier in the one or more second identifiers; Or / and, the second communication unit is used to perform at least one of the following: sending the first identifier to a second network device, the first identifier is used by the second network device to determine the UE policy associated with the first identifier; obtaining the policy rules associated with the first identifier from the second network device; obtaining the contract information associated with the first identifier from a third network device; obtaining the UE policy associated with the first identifier from the second network device.
45. The first network device according to claim 44, in, The second communication unit is used to send the first identifier to the second network device and receive the policy rules associated with the first identifier sent by the second network device.
46. The first network device according to claim 44, in, The second communication unit is used to send the first identifier to the third network device and receive the contract signing information associated with the first identifier sent by the third network device.
47. The first network device according to claim 44, in, The second communication unit is used to perform at least one of the following: sending the first identifier to the third network device and receiving the second association relationship sent by the third network device; sending the first identifier to the second network device and receiving the third association relationship and / or the first association relationship sent by the second network device.
48. The first network device according to any one of claims 41 to 47, in, The second processing unit is used to perform at least one of the following: determine the quality of service QoS rule associated with the first identifier based on the subscription information associated with the first identifier and / or the policy rule associated with the first identifier; determine the QoS parameter associated with the first identifier based on the subscription information associated with the first identifier and / or the policy rule associated with the first identifier; Based on the subscription information associated with the first identifier and / or the policy rule associated with the first identifier, a data packet detection rule PDR associated with the first identifier is determined.
49. The first network device according to claim 48, in, The second communication unit is used to perform at least one of the following: sending the quality of service QoS rules associated with the first identifier to the terminal device; sending the QoS parameters associated with the first identifier to an access network device, wherein the access network device serves the terminal device; sending the PDR associated with the first identifier to a fourth network device.
50. The first network device according to any one of claims 44 to 47, in, The second communication unit is used to perform one of the following: sending the UE policy associated with the first identifier to the terminal device; sending the first association relationship to the terminal device.
51. The first network device according to any one of claims 41 to 50, in, The first identifier is carried by at least one of the following: a registration request message, a registration update message, a session establishment request message, and a session modification request message.
52. The first network device according to any one of claims 41 to 51, in, The second communication unit is used to receive first indication information sent by the terminal device, wherein the first indication information is used to indicate at least one of the following: the terminal device supports reporting the first identifier, the terminal device can recognize the first identifier, and the terminal device can process the first identifier.
53. The first network device according to any one of claims 41 to 52, in, The second communication unit is used to send second indication information to the terminal device, wherein the second indication information is used to indicate at least one of the following: the network side supports processing the first identifier, the network side can identify the first identifier, the network side requests the terminal device to report the first identifier, the network side requires the terminal device to report the first identifier, and the network side allows the terminal device to report the first identifier.
54. The first network device according to claim 52, in, The first indication information is carried by the registration request message.
55. The first network device according to claim 53, in, The second indication information is carried by the registration acceptance message.
56. The first network device according to claim 49, in, The fourth network device is a user plane function UPF.
57. The first network device according to any one of claims 44 to 50, in, The second network device is a policy control function PCF; the third network device is a unified data management function UDM.
58. The first network device according to any one of claims 41 to 57, in, The first network device is an access and mobility management function AMF or a session management function SMF.
59. A terminal device, include: A transceiver, a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the terminal device executes the method as claimed in any one of claims 1 to 11.
60. A first network device, include: A transceiver, a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so that the first network device executes the method as claimed in any one of claims 12 to 29.
61. A chip, include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 11 or claims 12 to 29.
62. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 11 or claims 12 to 29.
63. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 19, or claims 1 to 11, or claims 12 to 29.
64. A computer program causing a computer to perform the method of any one of claims 1 to 11 or claims 12 to 29.
Citation Information
Patent Citations
Network slice selection method, terminal equipment and network equipment
CN106572516A
Information processing method, terminal device and storage medium
CN111406424A
Policy configuration method and apparatus, network device, and terminal
CN112088558A
Information configuration method and device, electronic equipment and storage medium
CN112491616A
Communication method and communication device
CN113630843A
