Communication methods, devices and systems

Abstract

This application provides a communication method, apparatus, and system. In this method, a first core network element can report a first number of users to a second core network element via first information. This first number of users is determined based on the characteristic information of the first service, specifically the number of users simultaneously using the first service by a first terminal user. Furthermore, the first core network element can determine the guaranteed bandwidth of the first service based on the first number of users and then report this guaranteed bandwidth to the second core network element via the first information. This ensures a guaranteed user experience when multiple users simultaneously use the first service.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a communication method, apparatus, and system. Background Technology

[0002] Currently, with the continuous development of tethering technology, multiple terminals can be connected to a single customer-premises equipment (CPE) or mobile phone. These multiple terminals can directly provide network access, which means that multiple users can be connected concurrently.

[0003] Currently, user plane function (UPF) entities can perceive the services of individual applications (APPs), thereby obtaining the quality of experience (QoE) results and / or quality deterioration results corresponding to different APP services. When a quality deterioration event occurs, the network data analytics function (NWDAF) can, based on the bandwidth required to ensure service experience, establish a dedicated bearer with guaranteed bit rate (GBR) or quality of service (QoS) flow identifier (QFI) to achieve the goal of service experience.

[0004] However, when multiple users are concurrent and based on the same business scenario, NWDAF, which is based on the single-user requirement for ensuring the APP business experience, is insufficient to support the experience assurance requirements of multiple concurrent users. Summary of the Invention

[0005] This application provides a communication method, apparatus, and system to improve service experience assurance during multi-user concurrency.

[0006] Firstly, a communication method is provided, which can be applied to a communication device. This communication device may be, for example, a first core network element, a component configured within the first core network element (such as a chip, chip system, processor, etc.), or a logic module or software capable of implementing all or part of the functions of the first core network element, etc. This application does not limit the scope of the application.

[0007] For example, the method includes: determining a first number of users based on characteristic information of a first service of a first terminal user, the first number of users being the number of users simultaneously using the first service; sending a first message, the first message including the first number of users, and / or, the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the first number of users.

[0008] Based on the above scheme, at least one user can simultaneously use the first service through the first terminal user. The first core network element can determine the number of users simultaneously using the first service through the first terminal user (denoted as the first user count) based on the characteristic information of the first service, and then report the first user count to the second core network element. Alternatively, it can determine the guaranteed bandwidth of the first service based on the first user count, and then report the guaranteed bandwidth of the first service to the second core network element. In this way, the user experience when multiple users use the first service simultaneously can be improved.

[0009] It is understood that the first user count is the sum of the number of concurrent users who use (or concurrently use) the first service through the first terminal user. The first user count and the concurrent user count can be used as equivalent concepts and can be used interchangeably in the following text, and should not constitute any limitation on this application.

[0010] In conjunction with the first aspect, in some possible implementations of the first aspect, the feature information includes at least one of the following: the number of concurrent flows of the first service, the start and end times of each flow in the concurrent flow, the timing relationship between different flows in the concurrent flow, traffic statistics, uplink and downlink messages, or rates.

[0011] For example, the first core network element can, based on the characteristic information of users using the first service within a period, calculate derived features of various characteristic information through different mathematical methods. Furthermore, based on the derived features of various characteristic information, artificial intelligence (AI) models or algorithms can be used to perceive the number of first users of the first service. In this way, the number of first users simultaneously using the first service can be determined.

[0012] It is understood that the feature information includes at least one of the following: the number of concurrent flows of the first service, the start and end time of each flow in the concurrent flow, the timing relationship between different flows in the concurrent flow, traffic statistics, uplink and downlink messages, or rates. This is just an example, and other indicators of the first service may also be included, but this application does not limit them.

[0013] In conjunction with the first aspect, in some possible implementations of the first aspect, the method further includes: receiving a second message, which is a poor quality event subscription request message, or a user experience document subscription request message, or a session establishment request message.

[0014] The second message and the aforementioned first message can interact through the Nupf interface, that is, the Nupf interface can extend the definition of the on / off switch or parameters of the sensing function for the number of users simultaneously using the first service through the first terminal user.

[0015] In other words, the first core network element can add the ability to sense the number of users simultaneously using the first service through the first terminal user, which can be added to the existing solution framework through interface definition.

[0016] Depending on the application scenario, this second message can be a different request message.

[0017] For example, for a solution that ensures the key business operations of VIP users, the second message can be a quality defect event subscription request message. Based on this second message, accurate quality defect perception and assurance processes can be achieved in multi-user concurrent scenarios.

[0018] For example, in scenarios where experience maps, user perception analysis results, or guarantee effect visualization are available, the second message can be a user experience document subscription request message. Based on this second message, the number of concurrent users can be displayed on the experience map, user perception analysis results, or guarantee effect visualization interface.

[0019] For example, in the PCC content billing and control solution, the second message can be a session establishment request message. Based on this second message, a business process for business processing can be implemented that recognizes different numbers of concurrent users and implements differentiated strategies and billing control.

[0020] Thus, different needs can be met based on this second message in different application scenarios.

[0021] In conjunction with the first aspect, in some possible implementations of the first aspect, determining the number of first users based on the characteristic information of the first service of the first terminal user includes: determining the number of first users based on the characteristic information of the first service of the first terminal user according to the first information in the second message, wherein the first information triggers the first core network element to perceive the number of users simultaneously using the first service; or, determining the number of first users based on the characteristic information of the first service of the first terminal user according to the local configuration of the first core network element taking effect, wherein the local configuration is used to configure the first core network element to perceive the number of users simultaneously using the first service.

[0022] One possibility is that, based on the first information in the second information, the first core network element can be enabled to increase its ability to perceive the number of users simultaneously using the first service. Thus, within a period, based on the characteristic information of the first terminal user using the first service, the first user can determine the number of users simultaneously using the first service through AI algorithms or models.

[0023] One possibility is that the first core network element can configure local settings via commands. Based on these local settings, the first core network element can increase its ability to perceive the number of users simultaneously using the first service. Thus, within a period, it can determine the number of users simultaneously using the first service based on the characteristic information of the first terminal users using the first service, through AI algorithms or models.

[0024] In this way, the first core network element can increase its ability to sense the number of users using the first service at the same time. This helps operators to accurately sense the state of multiple users using the first service in the network based on this function. As a result, it can achieve accurate perception, protection and management under the different service protection or differentiated billing and control strategies for different users (e.g., key services for VIP users).

[0025] In conjunction with the first aspect, in some possible implementations of the first aspect, the second message is a poor quality event subscription request message, and the first message also includes second information for characterizing poor quality results and / or QoE results, the second information being determined based on the first number of users.

[0026] The first core network element, by sensing and determining the first number of users, can adjust the algorithm or model used to obtain quality deviation results and / or QoE results based on this first number of users. For example, the first number of users can be used as an output parameter to optimize the quality deviation assessment and / or QoE assessment algorithm or model, making it adaptable to obtaining quality deviation results and / or QoE results in multi-user concurrent scenarios. Furthermore, the first core network element can obtain more accurate quality deviation results and / or QoE results based on the adjusted algorithm or model.

[0027] This helps operators to accurately perceive the concurrent status of primary services in the network based on this function, and to achieve accurate QoE assessment and quality degradation perception in key services for VIP users, and provide the necessary bandwidth guarantee for the experience.

[0028] In conjunction with the first aspect, in some possible implementations of the first aspect, the second message is a user experience document subscription request message, and the first message also includes a business experience quality (QoE) result, which is determined based on the first number of users.

[0029] The first core network element, by sensing and determining the first number of users, can adjust the algorithm or model used to obtain QoE results based on this number. For example, the first number of users can be used as an output parameter to optimize the QoE evaluation algorithm or model, making it adaptable to obtaining QoE results in multi-user concurrent scenarios. Furthermore, the first core network element can obtain more accurate QoE results based on the adjusted algorithm or model.

[0030] This helps operators accurately perceive the concurrent status of primary services and multiple users in the network, and achieve accurate QoE assessment for key services, providing the necessary bandwidth guarantee for a better user experience.

[0031] In conjunction with the first aspect, in some possible implementations of the first aspect, sending the first message includes: sending the first message when the number of users simultaneously using the first service by the first terminal user changes.

[0032] The first core network element can continuously monitor the number of first users. When the number of first users changes, it can trigger the first core network element to report the first message to the second core network element.

[0033] Optionally, when a quality deterioration event occurs, the first core network element can also be triggered to report the first message to the second core network element.

[0034] In this way, the number of users simultaneously using the first service through the first terminal user can be dynamically reported to the second core network element, which allows the second core network element to dynamically adjust the guaranteed bandwidth of the first service, thereby providing the users experiencing the first service with the necessary effective bandwidth guarantee.

[0035] In conjunction with the first aspect, in some possible implementations of the first aspect, the method further includes: determining the quality difference result and / or QoE result based on the first number of users.

[0036] Before obtaining the quality difference result and / or QoE result, the first core network element can adjust the algorithm (denoted as the first algorithm) used to obtain the quality difference result and / or QoE result based on the first number of users, and then obtain the quality difference result and / or QoE result based on the adjusted first algorithm.

[0037] In this way, more accurate quality difference and / or QoE results can be obtained.

[0038] In conjunction with the first aspect, in some possible implementations of the first aspect, the second message is a session establishment request message, and the first information includes a policy and charging control (PCC) matching rule, wherein the number of at least one candidate user simultaneously using the first service in the PCC matching rule corresponds one-to-one with at least one policy and charging control. The method further includes: determining a first policy and charging control based on the number of first users, wherein the first policy and charging control is the policy and charging control corresponding to the number of first users in the PCC matching rule.

[0039] The policy and charging control matching rules carried in the second message are supplemented with rule matching based on the number of first users. For example, different policies and charging controls can be applied to different numbers of first users. The first core network element can implement differentiated management and charging policies based on the policy and charging control matching rules carried in the second message, targeting different numbers of first users.

[0040] This helps operators generate new revenue or save network resources through differentiated management or billing package design.

[0041] Secondly, a communication method is provided, which can be applied to a communication device. This communication device may be, for example, a second core network element, a component configured within the second core network element (such as a chip, chip system, processor, etc.), or a logic module or software capable of implementing all or part of the functions of the second core network element, etc. This application does not limit the scope of the application.

[0042] For example, the method includes: determining a second message, the second message including first information, the first information being used to trigger a first core network element to perceive a first user count, the first user count being based on the number of users of a first terminal user simultaneously using a first service; and sending the second message.

[0043] Based on the above scheme, the second core network element enables the first core network element to sense the number of users simultaneously using the first service based on the first terminal user (denoted as the first user number) by carrying the first information in the second message it sends. In this way, the first core network element can be enabled to increase its ability to sense the number of users simultaneously using the first service, thereby improving the user experience when multiple users use the first service at the same time.

[0044] In conjunction with the second aspect, in some possible implementations of the second aspect, the second message is a poor quality event subscription request message, or the second message is a user experience document subscription request message.

[0045] In conjunction with the second aspect, in some possible implementations of the second aspect, the method further includes: receiving a first message, the first message including the first number of users, and / or, the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the first number of users.

[0046] In conjunction with the second aspect, in some possible implementations of the second aspect, the first message includes the first number of users, and the method further includes: determining the guaranteed bandwidth of the first service based on the first number of users.

[0047] The first message reported by the first core network element to the second core network element includes the first number of users. In this case, the second core network element can determine the guaranteed bandwidth of the first service when n users of the first terminal user use the first service at the same time based on the first number of users and the guaranteed bandwidth when a single user uses the first service. Here, n represents the first number of users.

[0048] In this way, the second core network element can increase its calculation capability based on the number of first users when calculating the guaranteed bandwidth of the first service.

[0049] In conjunction with the second aspect, in some possible implementations of the second aspect, the second message is a poor quality event subscription request message, and the first message also includes second information used to characterize the poor quality result and / or the business experience quality (QoE) result, which is determined based on the first number of users.

[0050] In conjunction with the second aspect, in some possible implementations of the second aspect, the second message is a user experience document subscription request message, and the first message also includes a business experience quality (QoE) result, which is determined based on the first number of users.

[0051] In conjunction with the second aspect, in some possible implementations of the second aspect, the first message is a user experience perception information notification message, and the method further includes: based on the first message, determining at least one of the following: an experience map, user perception analysis results, or a visual interface for guaranteeing effects.

[0052] The second core network element can generate at least one of the following based on the received first message: an experience map, user perception analysis results, or a visual interface for guarantee effect, and at least one of the experience map, user perception analysis results, or visual interface for guarantee effect can present an indicator of the number of first users.

[0053] In this way, the actual operating status of the primary service on the network can be reflected, which helps operators to observe the distribution of concurrent users of the primary service on the current network through visual analysis, and facilitates the design of differentiated management or billing packages in the next step.

[0054] In conjunction with the second aspect, in some possible implementations of the second aspect, the first message is also used to characterize a change in the number of users simultaneously using the first service for the first account.

[0055] In other words, the first core network element can continuously monitor the number of first users, and when the number of first users changes, it can trigger the first core network element to report the first message to the second core network element.

[0056] Optionally, when a quality deterioration event occurs, the first core network element can also be triggered to report the first message to the second core network element.

[0057] In this way, the second core network element can dynamically adjust the guaranteed bandwidth of the first service based on the number of users simultaneously using the first service through the first terminal user reported by the first core network element, thereby providing the users experiencing the first service with the necessary effective bandwidth guarantee.

[0058] In conjunction with the second aspect, in some possible implementations of the second aspect, the method further includes: determining the adaptive bit rate (ABR) based on the first number of users.

[0059] The second core network element can further determine the ABR based on the first number of users carried in the first received message.

[0060] In this way, the second core network element can increase its calculation capability based on a multiple of the number of first users when determining the ABR.

[0061] In conjunction with the second aspect, in some possible implementations of the second aspect, the second core network element is a session management function (SMF) network element, and the element further includes: receiving a third message from a policy control function (PCF), the third message including the first information.

[0062] That is, the third message may include the first information used to trigger the first core network element to perceive the first number of users, which is based on the number of users of the first terminal user who are simultaneously using the first service.

[0063] The third message can be interacted with through the N7 interface, which means that the N7 interface can be extended to define the on / off switch or parameters of the sensing function for the number of users simultaneously using the first service through the first terminal user.

[0064] In other words, the PCF can send a third message to the SMF via the N7 interface. Correspondingly, the SMF can receive a third message from the PCF via the N7 interface.

[0065] Similarly, when the SMF sends a second message to the first core network element, the second message can be interacted with through the N4 interface. That is, the N4 interface can be extended to define the switch or parameters of the sensing function for the number of users who simultaneously use the first service through the first terminal user.

[0066] In other words, the SMF can send a second message to the first core network element through the N4 interface. Correspondingly, the first core network element can receive the second message from the SMF through the N4 interface.

[0067] In other words, the first core network element can add the ability to sense the number of users simultaneously using the first service through the first terminal user, which can be added to the existing solution framework through interface definition.

[0068] This allows operators to accurately perceive the concurrent status of multiple users for the primary service in the network based on this function, thereby enabling differentiated management or billing package design, bringing new revenue to operators or saving network resources.

[0069] In conjunction with the second aspect, in some possible implementations of the second aspect, the second core network element is the PCF.

[0070] That is, the second message sent by the PCF to the SMF can carry the first information, which is used to trigger the first core network element to perceive the first number of users. The first number of users is based on the number of users who are simultaneously using the first service by the first terminal user.

[0071] It is understood that the second message sent by the PCF to the SMF and the third message sent by the PCF to the SMF via the N7 interface are the same message. They are only given different names to distinguish which core network element the second core network element is, and should not constitute any limitation on the embodiments of this application.

[0072] For example, when the second core network element is PCF, PCF sends the second message to SMF; when the second core network element is SMF, PCF sends the third message to SMF, and SMF sends the second message to the first core network element.

[0073] In conjunction with the second aspect, in some possible implementations of the second aspect, the first information includes policy and charging control matching rules, wherein the policy and charging control matching rules correspond one-to-one with at least one policy and charging control based on the number of at least one candidate user who simultaneously uses the first service by the first terminal user.

[0074] The first information included in the second and third messages above includes policy and billing control matching rules, and different numbers of users can correspond to different policies and billing controls.

[0075] This allows operators to generate new revenue or save network resources by designing differentiated management or billing packages for different numbers of users.

[0076] For details regarding the second aspect, please refer to the detailed explanation in the first aspect; further elaboration will not be repeated here.

[0077] Thirdly, this application provides a communication device, including modules or units for implementing the methods of the first aspect and any possible implementation thereof. Each module or unit can implement its corresponding function by executing a computer program.

[0078] Fourthly, this application provides a communication device, including a processor, the processor being configured to execute the communication method described in the first aspect and any possible implementation thereof.

[0079] The device may further include a memory for storing instructions and data. The memory is coupled to the processor, which, when executing the instructions stored in the memory, can implement the methods described in the foregoing aspects. The device may also include a communication interface for communicating with other devices; exemplary, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0080] For example, the device in the third or fourth aspect is a first core network element, or a component in the first core network element, such as a chip, chip system, processor, etc.

[0081] Fifthly, this application provides a chip system including at least one processor for supporting the implementation of the functions involved in the first aspect and any possible implementation of the first aspect, such as receiving or processing information involved in the above methods.

[0082] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0083] The chip system can consist of chips or include chips and other discrete components.

[0084] Sixthly, this application provides a communication device, including modules or units for implementing the methods of the second aspect and any possible implementation of the second aspect. Each module or unit can implement its corresponding function by executing a computer program.

[0085] In a seventh aspect, this application provides a communication device, including a processor, the processor being configured to execute the communication method described in the second aspect and any possible implementation thereof.

[0086] The device may further include a memory for storing instructions and data. The memory is coupled to the processor, which, when executing the instructions stored in the memory, can implement the methods described in the foregoing aspects. The device may also include a communication interface for communicating with other devices; exemplary, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

[0087] For example, the device in the sixth or seventh aspect is a second core network element, or a component in the second core network element, such as a chip, chip system, processor, etc.

[0088] Eighthly, this application provides a chip system including at least one processor for supporting the implementation of the functions involved in the second aspect and any possible implementation of the second aspect, such as receiving or processing information involved in the above methods.

[0089] In one possible design, the chip system also includes a memory for storing program instructions and data, which may be located within or outside the processor.

[0090] The chip system can consist of chips or include chips and other discrete components.

[0091] Ninthly, this application provides a computer-readable storage medium including a computer program that, when run on a computer, causes the computer to implement the methods of the first or second aspect and any possible implementation of the first or second aspect.

[0092] In a tenth aspect, this application provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform the methods of the first or second aspect and any possible implementation thereof.

[0093] Eleventhly, embodiments of this application provide a communication system, including the aforementioned first core network element and second core network element.

[0094] The third to eleventh aspects of this application correspond to the technical solutions of the first and second aspects of this application. The beneficial effects achieved by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

[0095] Figure 1 This is a schematic diagram of the architecture of a communication system applicable to the communication method provided in this application;

[0096] Figure 2 This is a schematic diagram of the hot technologies provided in the embodiments of this application;

[0097] Figure 3 This is a schematic diagram of the NWDAF data subscription collection, data analysis, and analysis result subscription and notification mechanism provided in the embodiments of this application;

[0098] Figure 4 This is a schematic flowchart of the communication method provided in the embodiments of this application;

[0099] Figure 5 This is another illustrative flowchart of the communication method provided in the embodiments of this application;

[0100] Figure 6 This is a diagram of the QoE and / or quality difference assessment algorithm architecture provided in the embodiments of this application;

[0101] Figure 7 This is another illustrative flowchart of the communication method provided in the embodiments of this application;

[0102] Figure 8 This is another illustrative flowchart of the communication method provided in the embodiments of this application;

[0103] Figure 9 This is another schematic diagram of a network system architecture provided in the embodiments of this application;

[0104] Figure 10 This is a schematic diagram of the communication device provided in the embodiments of this application;

[0105] Figure 11 This is a schematic diagram of another communication device provided in the embodiments of this application. Detailed Implementation

[0106] The technical solution provided in this application will now be described with reference to the accompanying drawings.

[0107] To facilitate understanding of the embodiments of this application, the following points will be explained first:

[0108] First, in this application, the indication includes explicit indication (also known as direct indication) and implicit indication (also known as indirect indication). Explicit indication information A means including information A; implicit indication information A means indicating information A through the correspondence between information A and information B, and through direct indication information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured; or it can refer to indicating information A through information B and preset rules.

[0109] Second, in this application, information C is used to determine information D, which includes both determining information D based solely on information C and determining it based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, in the case where information D is determined based on information E, and information E is determined based on information C.

[0110] Third, in this application, "at least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates an "or" relationship between the preceding and following related objects, but it does not exclude the possibility of indicating an "and" relationship. The specific meaning can be understood in the context. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a and b and c. Here, a, b, and c can be single or multiple.

[0111] Fourth, in this application, the use of prefixes such as "first" and "second" is merely for the purpose of distinguishing and describing different things belonging to the same category, and does not constrain the order, size, or quantity of things. For example, "first message" and "second message" are simply different messages, and there is no chronological, size, or priority relationship between them.

[0112] Fifth, in this application, "send" and "receive" indicate the direction of signal transmission. For example, "send information to the first core network element" can be understood as the destination of the information being the first core network element, which may include direct transmission via the air interface or indirect transmission via the air interface from other units or modules. "Receive information from the second core network element" can be understood as the source of the information being the second core network element, which may include direct reception from the second core network element via the air interface or indirect reception from the second core network element via the air interface from other units or modules. "Send" can also be understood as the "output" of the chip interface, and "receive" can also be understood as the "input" of the chip interface.

[0113] In other words, sending and receiving can be done between devices, such as between the first core network element and the second core network element; or it can be done within a device, such as between components, modules, chips, software modules, or hardware modules within the device via a bus, wiring, or interface.

[0114] The technical solutions provided in this application can be applied to various communication systems, such as: Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, sidelink (SL) communication systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication systems, 5th Generation (5G) mobile communication systems, or new radio access technology (NR). Among these, 5G mobile communication systems can include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems, such as 6th Generation (6G) mobile communication systems. This application does not limit these applications.

[0115] Figure 1 This is a schematic diagram of a network system architecture applicable to the methods provided in the embodiments of this application. As shown in the figure, the network system architecture mainly includes: terminal equipment, radio access network (RAN) equipment, and core network equipment.

[0116] Terminal equipment, also known as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device.

[0117] A terminal device is a device with wireless transceiver capabilities. It can communicate with one or more core network (CN) devices (or core devices) via access network devices (or access equipment) in a wireless access network. Terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water (such as ships); and they can be deployed in the air (such as airplanes, balloons, and satellites). In this embodiment, the terminal device can be a terminal device in an Internet of Things (IoT) system, for example, an ambient Internet of Things (A-IoT, or AIoT) device. IoT is an important component of future information technology development. Its main technical characteristic is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. Connections can be made using broadband technology or narrowband (NB) technology. IoT technology, for example, can achieve massive connectivity, deep coverage, and low terminal power consumption through narrowband technology.

[0118] In this embodiment, the device for implementing the functions of the terminal device can be the terminal device itself, or it can be any device capable of supporting the terminal device in implementing those functions, such as a chip system. This device can be installed in or used in conjunction with the terminal device. In this embodiment, the chip system can be composed of chips or may include chips and other discrete components. This embodiment only uses the terminal device as an example to illustrate the device for implementing the functions of the terminal device, and does not constitute a limitation on the solution of this embodiment.

[0119] The terminal device in this application can be a hardware device, a software function running on dedicated hardware, or a software function running on general-purpose hardware. It can also be a virtualized device, for example, implemented through general-purpose hardware and instantiated virtualization functions, or dedicated hardware and instantiated virtualization functions. Among them, the general-purpose hardware can be a server, such as a cloud server.

[0120] In the embodiments of this application, the wireless access network device can be any device with wireless transceiver capabilities. The wireless access network device can provide wireless communication services, enabling terminal devices to access the wireless network. The wireless access network can also be referred to as an access network device or a network device. The wireless access network device can also be called a RAN node or an access network device.

[0121] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a 6th-generation (6G) mobile communication system, or a base station in a future mobile communication system. A RAN node can be a macro base station, a micro base station, an indoor station, a relay node, a donor node, or a radio controller in a cloud radio access network (CRAN) scenario. Optionally, a RAN node can also be a server.

[0122] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0123] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an open access network (open RAN, O-RAN, or ORAN) system, CU can also be called an open CU (O-CU), DU can also be called an O-DU, CU-CP can also be called an O-CU-CP, CU-UP can also be called an O-CU-UP, and RU can also be called an O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through a software module, a hardware module, or a combination of software and hardware modules.

[0124] The core network functions of mobile communication networks (such as 5G, 6G, etc.) include: network slice selection function (NSSF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management (UDM), application function (AF), edge application server discovery function (EASDF), network slice specific authentication and authorization function (NSSAAF), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), service communication proxy (SCP), network slice admission control function (NSACF), user plane function (UPF), and data network (DN), etc.

[0125] Among them, NSSF can be used to select a suitable network slice instance for the UE: single network slice selection assistance information (S-NSSAI).

[0126] The NEF can be used to open up services and capabilities provided by the 3rd generation partnership project (3GPP) network function (NF) to the AF, while also obtaining external application information from the AF. In other words, the NEF can provide interfaces for third-party applications, such as application programming interfaces (APIs).

[0127] NRF is used to implement NF service registration and discovery.

[0128] PCF primarily controls policies such as Quality of Service (QoS) and charging.

[0129] UDM primarily handles access authentication, user identification, authentication / authorization, mobility and mobility management, etc.

[0130] Application Providers (AFs) primarily relay application-side requests to the network side and can be viewed as application servers or their proxies. They can provide certain application-layer services to terminal devices. When providing services to terminal devices, AFs have requirements regarding billing and QoS policies and need to notify the network. Simultaneously, AFs also require application-related information from core network devices.

[0131] EASDF primarily supports the dynamic positioning of edge application servers (EAS) in edge computing scenarios.

[0132] NSSAAF can provide independent authentication / authorization processes for different slices.

[0133] AUSF primarily provides unified access authentication services for both 3GPP and non-3GPP systems.

[0134] The AMF (Active Mobility Controller) primarily performs functions such as mobility management and access authentication / authorization. In addition, the AMF network element can also be responsible for transmitting user policies between terminal devices and the PCF (Programmable Controller Network) network element.

[0135] SMF primarily performs tasks such as session management, allocation and management of Internet Protocol (IP) addresses for user devices, and UPF selection.

[0136] SCP serves as a control plane message routing intermediary, enabling inter-NF communication.

[0137] NSACF can perform slice-level session admission control.

[0138] UPF is primarily used for packet routing and forwarding, policy and QoS processing, and usage reporting. UPF is an interface that supports Data Networking (DN) and can perform functions such as user plane data forwarding, session / flow-based billing statistics, and bandwidth limiting. User data can be sent to data networks (such as the Internet) through this network element.

[0139] DN primarily provides business services to users.

[0140] The network elements communicate with each other through interfaces. For example, the signaling plane interface between the terminal equipment and the AMF is interface N1. Since the terminal equipment cannot directly interact with the core network equipment, it needs to pass through the access stratum (AS) to transmit non-access stratum (NAS) information. The signaling plane interface through which the AMF requests resources for protocol data unit (PDU) sessions from the access network (AN) is interface N2. The signaling plane interface between the UPF and SMF is interface N4, and so on. These are not elaborated upon, and this application does not limit them.

[0141] The above description of the various network elements in the core network and the interfaces between them is merely illustrative and should not constitute any limitation on this application. Furthermore, the network elements shown in the diagram can be understood as network elements in the core network used to implement different functions, such as network slices that can be combined as needed. These core network elements can be independent devices or integrated into the same device to implement different functions; this application does not limit the specific form of the aforementioned network elements.

[0142] It is understood that the network elements used in future communication systems may be any of the aforementioned network elements, or network elements with the same or similar functions under other names; this application does not limit this.

[0143] In this embodiment, access network devices and core network elements can be collectively referred to as network devices. The apparatus used to implement the functions of a network device can be a network device itself; it can also be an apparatus capable of supporting the network device in implementing those functions, such as a chip system, hardware circuit, software module, or a hardware circuit plus a software module. This apparatus can be installed in the network device or used in conjunction with the network device. In this embodiment, the example of a network device being used to implement the functions of a network device is used only, and does not constitute a limitation on the solutions of this embodiment.

[0144] The network device in this application can be a hardware device, a software function running on dedicated hardware, or a software function running on general-purpose hardware. It can also be a virtualized device, for example, implemented through general-purpose hardware and instantiated virtualization functions, or dedicated hardware and instantiated virtualization functions. Among them, the general-purpose hardware can be a server, such as a cloud server.

[0145] Figure 2 This is a schematic diagram of hotspot technology provided in an embodiment of this application. The hotspot function originated from the introduction of shared hotspot devices such as Wireless Fidelity (Wi-Fi) and Mobile Wi-Fi (MiFi). That is, a mobile communication data card or CPE can directly provide Wi-Fi hotspots to different terminal devices, such as laptops, smartphones, tablets, etc. Users can enable the hotspot function on different terminal devices; the terminal device providing the hotspot function can be called a hotspot user.

[0146] in, Figure 2 (a) shows a smartphone providing a Wi-Fi hotspot to different terminal devices via a Wi-Fi connection; Figure 2 (b) shows how a smartphone provides a hotspot to different terminal devices via a physical connection using a universal serial bus (USB).

[0147] Figure 2 (c) shows a smartphone providing a hotspot to different terminal devices via Bluetooth connection.

[0148] Figure 3 This is a schematic diagram illustrating the NWDAF data subscription collection, data analysis, and analysis result subscription and notification mechanism provided in this application embodiment. Figure 3 The solid lines in the diagram represent the data analysis and assurance process, the dashed line 'a' represents the subscription process, and the dashed line 'b' represents the data generation process.

[0149] from Figure 3 As can be seen, PCF includes the following modules: intelligent decision-making, VIP subscription packages, NWDAF addressing, and PCF session management. Among them, intelligent decision-making includes ensuring dynamic rules, generating guarantee policies, and QoS decisions.

[0150] SMF includes the following modules: SMF session management and data subscription management.

[0151] UPF comprises the following modules: UPF session management and event reporting. Event reporting includes data subscription management, live stream identification, data stream (key performance indicator, KPI) generation, and quality / discretion analysis. UPF's main functions also include: business awareness of user access data packets, policy and billing control, and data forwarding. UPF can report flow descriptions, traffic, time, experience data, and quality / discretion analysis results for business access.

[0152] NWDAF comprises the following modules: the analytics logical function (AnLF) and the data platform. AnLF includes analytics subscription management, UPF addressing, generation of assurance policies and QoS, assurance effectiveness evaluation, visualization, and assurance SMS notifications; the data platform includes data collection and distribution of low-quality subscriptions.

[0153] For details regarding the NWDAF data subscription collection, data analysis, and analysis result subscription and notification mechanisms, please refer to the relevant explanations in 3GPP technical specification (TS) 23.288, which will not be repeated here.

[0154] Based on the relevant content defined in the aforementioned 3GPP standard protocols, operators launch VIP (Very Important Person) key service protection packages, configuring services related to this package in the Business & Operations Support System (BOSS) and PCF. The User Data Gateway (UDG) deploys SA (Service Assistance) service identification capabilities, enabling it to identify protected app flows. Operations, Administration and Maintenance (OAM) can periodically report radio metrics to the NWDAF. The specific process is as follows:

[0155] 1. The BOSS issues a VIP key business protection package to PCF.

[0156] 2. After the PCF configures new package information, if the package is bound to an analytics identifier (analytics ID), such as an analytics identifier that can be used to identify quality assurance, the PCF can send a subscription quality assurance data analytics message to the NWDAF (for example, through the Nndwaf_EventSubscription_Notify message) to initiate a subscription quality assurance policy. The PCF can also send the corresponding rules and application function application identifier (af APP ID) and other key information to the NWDAF.

[0157] 3. Based on the analytics ID carried in the subscription message issued by the PCF, the NWDAF determines that data needs to be collected from the UPF and RAN, and then initiates a user experience data subscription request to the UPF.

[0158] For example, NWDAF sends a subscription data collection request message to SMF (for example, via the Nsmf_EventExposure_Subscribe message). SMF then sends the subscription data collection to UPF. The subscription data collection request message carries key information such as rules and af APP ID. UPF can then use this rule and af APP ID to determine which users' APP streams need to undergo quality defect detection.

[0159] NWDAF can use tracking area identity (TAI) information to locate the UPF that provides VIP service guarantee within the area coverage, and subscribe to the UPF for quality information of the VIP package group.

[0160] NWDAF can send subscription request messages to UPF to request UPF to report experience data.

[0161] For example, NWDAF can send a poor-quality event subscription request message to UPF, which could be, for example, a poor-quality event subscription request message for VIP user apps.

[0162] Accordingly, UPF can report VIP user app quality issues to NWDAF.

[0163] For example, NWDAF can send a user experience document subscription request message to UPF, which can be a regular user experience document subscription request message.

[0164] Accordingly, UPF can report user-level business experience awareness information notification messages to NWDAF.

[0165] 4. The signed VIP package is initially activated through PCF session management, SMF session management, and UPF session management. UPF can determine the type of service accessed by the user and match it with the af APP ID in the rules carried in the subscription message issued by NWDAF. If the match is consistent, the quality detection of the APP service will be initiated. When a quality defect event occurs, UPF can send collected data to NWDAF (for example, through the Nupf_EventExposure_Notify message) to report the quality defect event.

[0166] 5. After receiving a poor quality event, NWDAF can extract the AF APP ID and obtain information such as the guaranteed bandwidth and latency required by the APP; it can also initiate QoS guarantee recommendations to PCF by extracting key information such as the flow 5-tuple. For example, NWDAF can send a message to PCF to obtain the data analysis results of poor quality guarantee (for example, through the Nnwdaf_EventSubscription_Notify message).

[0167] 6. PCF triggers UPF to activate dedicated load. PCF makes a comprehensive decision on whether to formally issue a guarantee policy to the user based on the user's quota and other policy information (if the policy conflicts with NEF, NWDAF can be configured with high priority), generates dynamic rules carrying guaranteed bit rate (GBR) (or guaranteed bandwidth) information for dedicated load or QoS flow identifier (QFI), and notifies SMF and AMF to establish dedicated load.

[0168] 7. PCF sends a notification of the payload establishment result to NWDAF (for example, via the Nndwaf_EventsSubscription_Subscribe message).

[0169] SMF triggers UPF, RAN establishes dedicated bearer successfully, and service data is transmitted on GBR dedicated bearer or QFI, with transmission bandwidth and processing latency being prioritized and guaranteed, thus improving the service experience.

[0170] Based on the current solution, different services can be perceived through UPF to obtain QoE results. When a subscribed user is identified in a scenario where service quality deteriorates, i.e., a quality deterioration event occurs, NWDAF can improve the experience of key services by establishing a dedicated bearer or QFI with GBR protection based on the bandwidth required to ensure service experience.

[0171] However, the current solution is based on the business experience guarantee requirements of a single user and is insufficient to support the business experience guarantee requirements in multi-user concurrent scenarios.

[0172] For example, QoE results and / or quality deterioration results are obtained based on a single user's perception of a particular service. In other words, current QoE assessment and / or quality deterioration judgment algorithms or models are designed for a single user. However, when multiple terminals are connected to a single CPE or mobile phone, or when multiple users are using the same service concurrently, the QoE results and / or quality deterioration judgments obtained based on current algorithms or models are inaccurate.

[0173] For example, in scenarios where critical services suffer from poor quality assurance, NWDAF can recommend guaranteed bandwidth based on the bandwidth requirements of a single user's service experience. Therefore, in scenarios with multiple concurrent users, the guaranteed bandwidth recommended by NWDAF is insufficient to support the experience assurance requirements of multiple concurrent users.

[0174] In view of this, this application provides a communication method in which a first core network element can determine the number of users simultaneously using the first service through a first terminal user (denoted as the first user count) based on the characteristic information of the first service, and then report the first user count to a second core network element. Alternatively, it can determine the guaranteed bandwidth of the first service based on the first user count, and then report the guaranteed bandwidth of the first service to the second core network element. This ensures a guaranteed user experience when multiple users simultaneously use the first service. For example, it can ensure the bandwidth requirements when multiple users simultaneously use the first service, and also improve the accuracy of the QoE results and / or poor quality results obtained when multiple users simultaneously use the first service.

[0175] The methods provided in the embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0176] Figure 4 This is a schematic flowchart of the communication method provided in the embodiments of this application. Figure 4 The method provided in this application is described using the perspective of a first core network element as an example, but this should not constitute any limitation on this application. Furthermore, Figure 4 The first core network element can also be replaced by components in the first core network element, such as chips, chip systems, processors, etc., or by logic modules or software that can realize some or all of its functions. This application does not limit this.

[0177] The first core network element may be, for example, a UPF, etc., but this application does not limit this embodiment.

[0178] See Figure 4 , Figure 4The method 400 shown may include steps 410 to 420, and the steps in method 400 are described in detail below.

[0179] In step 410, the first core network element determines the number of first users based on the characteristic information of the first service of the first terminal user. The number of first users is the number of users who use the first service at the same time.

[0180] For example, the first service may include the services of one or more apps. For instance, the one or more apps may include APP#1, APP#2, ..., APP#N, etc. Different apps may correspond to the same service or different services.

[0181] Alternatively, the first service may also include the same type of service from the same type of APP. For example, the first service may include the same service from the following types of APPs: live streaming APP, game APP, chat APP, etc. Among them, the first service is the live streaming service of the live streaming APP, such as the live streaming APP may include APP#1, APP#2, the first service is the game service of the game APP, such as the game APP may include APP#3, APP#4, etc., and this application embodiment does not limit this.

[0182] In other words, the first business can include one or more businesses, or it can include a type of business, that is, it can include multiple businesses.

[0183] The first core network element can support the monitoring of the number of first users for multiple services. In actual monitoring, the first core network can calculate feature information for each individual service, and thus the obtained number of first users is specific to that individual service.

[0184] If a single business corresponds to multiple apps, feature information can be further calculated based on different apps to determine the first number of users corresponding to that app.

[0185] For example, a CPE can host six users, two of whom are simultaneously using the game service of the game APP, three of whom are simultaneously using the live streaming service of live streaming APP #1, and one user is simultaneously using the live streaming service of live streaming APP #2. In other words, the APPs corresponding to the live streaming services include live streaming APP #1 and live streaming APP #2.

[0186] In this case, the first core network element can determine the number of users simultaneously using the game service based on the feature information corresponding to the game service of the game APP as 2; the number of users simultaneously using the live streaming service based on the feature information corresponding to the live streaming service of live streaming APP #1 as 3; and the number of users simultaneously using the live streaming service based on the feature information corresponding to the live streaming service of live streaming APP #2 as 1.

[0187] The first terminal user can provide hotspot service to at least one user, who can then access the network through the hotspot and use different services. For example, the at least one user can use the first service simultaneously.

[0188] Alternatively, the first terminal user can provide an account for at least one user to use the first service; that is, at least one user can use the same service through the first terminal user's first account. This at least one user can share the same account with the first terminal user to use the same service.

[0189] From the network's perspective, only the traffic generated by the first end user (i.e., the terminal device or CPE that connects to the network and enables a hotspot) when using the first service is monitored. For example, regarding APP#1, the first end user can access APP#1 by logging into a first account, and multiple different users can also access APP#1 simultaneously by logging into the same first account. In this case, the network can monitor the traffic generated by the first end user when using the first service.

[0190] Therefore, the first core network element cannot directly obtain the number of users simultaneously using the first service through the first terminal user. In other words, the first core network element cannot know the actual number of users using the first service.

[0191] Based on this, the first core network element can obtain the first number of users through the characteristic information of the first service. The first number of users is the number of users who use the first service simultaneously through the first terminal user.

[0192] It is understood that the first user count can also be referred to as the number of concurrent users using the first service simultaneously through the first terminal user, and the number of concurrent users can be understood as the total number of users using the first service simultaneously, etc. This application embodiment does not limit this.

[0193] It should also be understood that the number of first users simultaneously using the first service through the first terminal user can also be called the number of concurrent users of the APP, that is, the number of concurrent users simultaneously using the same or the same type of APP through the first terminal user. Here, APP can correspond to the first service, and the number of first users corresponds to the number of concurrent users. The two terms are different, but express the same meaning. The following text may use the terms "number of first users" or "number of concurrent users of the APP" interchangeably, and this should not constitute any limitation on the embodiments of this application.

[0194] Optionally, the feature information includes at least one of the following: the number of concurrent flows of the first service, the start and end time of each flow in the concurrent flow, the timing relationship between different flows in the concurrent flow, traffic statistics, uplink and downlink messages, or rates.

[0195] The traffic statistics information can be understood as, for example, the uplink and downlink traffic of the first service, the total traffic, the ratio of uplink and downlink traffic, and the traffic transmitted by the first service within this period. This application embodiment does not limit this information.

[0196] The first core network element can perform calculations based on the aforementioned feature information using different mathematical methods to obtain derived features for each feature. Furthermore, based on these derived features, AI models or algorithms can be used to achieve real-time perception of the number of first users.

[0197] For example, mathematical methods for calculating derived features may include at least one of the following: minimum value, maximum value, total length, number of packets, quartiles and their differences, median, quartiles and their differences, median, mean, variance, standard deviation, third moment, fourth moment, kurtosis, skewness, absolute median difference, power-law distribution, etc., which are not limited in the embodiments of this application.

[0198] It is understood that the feature information includes at least one of the following: the number of concurrent flows of the first service, the start and end time of each flow in the concurrent flow, the timing relationship between different flows in the concurrent flow, traffic statistics, uplink and downlink messages, or rates. This is just an example, and may also include other types of behavioral features, etc. The embodiments of this application do not limit this.

[0199] As an example, the first core network element uses an AI model or algorithm to achieve real-time perception of the number of concurrent users accessing the first service within a period (e.g., every 5 seconds is a period), the start and end time of each flow in the concurrent flow, the temporal relationship between different flows in the concurrent flow, traffic statistics, uplink and downlink packets, or rates. Through perception, the first core network element can obtain the number of first users who simultaneously use the first service through the first terminal user.

[0200] It is understood that the method for obtaining the first number of users provided in step 410 above is only an example, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application, or other feature engineering, models, algorithms, and solutions that can realize real-time perception of the first number of users of the first service, should be covered within the scope of protection of this application.

[0201] In step 420, the first core network element sends a first message, which includes the first number of users and / or the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the first number of users.

[0202] For example, a first core network element can report the number of users simultaneously using the first service, obtained through sensing, to a second core network element via a first message. This second core network element could be, for example, an NWDAF (Network-Driven Assisted Network). Furthermore, the second core network element can, based on the number of users and the guaranteed bandwidth for a single user using the first service, obtain the guaranteed bandwidth for n users simultaneously using the first service. Here, n represents the number of users, and the guaranteed bandwidth reflects the bandwidth requirements for ensuring a good user experience for the first service.

[0203] For example, the guaranteed bandwidth of the first service is equal to the number of first users n multiplied by the guaranteed bandwidth when a single user uses the first service.

[0204] In another example, the first core network element can obtain the guaranteed bandwidth when n users simultaneously use the first service, which is also the guaranteed bandwidth of the first service, based on the number of first users simultaneously using the first service and the guaranteed bandwidth when a single user uses the first service. Here, n represents the number of first users.

[0205] Furthermore, the first core network element can report the guaranteed bandwidth of the first service to the second core network element via a first message, providing the second core network element with a suggested guaranteed bandwidth for the first service. The second core network element can then determine the actual guaranteed bandwidth for the first service based on the suggested guaranteed bandwidth indicated by the first message. This second core network element could be, for example, an NWDAF (Network WDAF).

[0206] It is understood that the method provided in step 420 above for the first core network element or the second core network element to determine the guaranteed bandwidth of the first service based on the first number of users is only an example. However, the scope of protection of this application is not limited to this. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application, or other messages and processes that can achieve accurate guaranteed bandwidth calculation, should be covered within the scope of protection of this application.

[0207] Based on the above technical solution, at least one user of the first terminal user can simultaneously use the first service. The first core network element can determine the number of users simultaneously using the first service through the first terminal user (denoted as the first user count) based on the characteristic information of the first service, and then report the first user count to the second core network element. Alternatively, it can determine the guaranteed bandwidth of the first service based on the first user count, and then report the guaranteed bandwidth of the first service to the second core network element. In this way, the user experience when multiple users simultaneously use the first service can be improved.

[0208] The methods provided in the embodiments of this application will be described in detail below for different scenarios.

[0209] Scenario 1: A solution for ensuring key business operations for VIP users, enabling accurate quality deviation detection and process assurance in multi-user concurrent scenarios.

[0210] Figure 5 This is another illustrative flowchart of the communication method provided in the embodiments of this application. Figure 5 The method 500 shown is based on Figure 4 Based on method 400, another processing logic of the communication method is shown. Method 500 is based on method 400, and describes the method provided in this application from the perspective of the interaction between the first core network element, the second core network element, the PCF, and the AMF, but this should not constitute any limitation on this application.

[0211] also, Figure 5 The first core network element can also be replaced by components in the first core network element, such as chips, chip systems, processors, etc., or by logic modules or software that can realize some or all of its functions. Figure 5 The second core network element can also be replaced by components in the second core network element, such as chips, chip systems, processors, etc., or by logic modules or software that can realize some or all of its functions; the PCF or AMF can also be replaced by components in the PCF or AMF, such as chips, chip systems, processors, etc., or by logic modules or software that can realize some or all of its functions, and this application does not limit this.

[0212] The following text focuses on describing the steps that differ from those in Method 400. For explanations of the steps that are the same as those in Method 400, as well as the same terms, please refer to the relevant descriptions above, which will not be repeated here.

[0213] For example, the first core network element may be a UPF, the second core network element may be an NWDAF, etc., and the embodiments of this application do not limit this.

[0214] It should be noted that, Figure 5The first core network element, the second core network element, the first terminal user, the SMF, the PCF, and the AMF shown are merely examples and should not constitute any limitation on the embodiments of this application.

[0215] See Figure 5 , Figure 5 The method 500 shown may include steps 501 to 515, and the steps in method 500 are described in detail below.

[0216] In step 501, the second core network element determines a second message, which includes first information. The first information is used to trigger the first core network element to perceive the first number of users, which is based on the number of users of the first terminal user who are simultaneously using the first service.

[0217] For example, the second message is a poor-quality event subscription request message (exemplarily, it could be a Nupf_EventExposure_Subscribe Request message), which could be, for example, a VIP user APPs poor-quality event subscription request message.

[0218] When a second core network element sends a poor-quality event subscription request message to a first core network element, it can extend the message with first information to trigger the first core network element to perceive the first number of users. In other words, the message can be extended with the ability to perceive the first number of users (or concurrent users) for multiple services.

[0219] For details regarding the first number of users, the first terminal user, and the first service, please refer to the detailed explanation in Method 400, which will not be repeated here.

[0220] The second message is a VIP user APP quality deterioration event subscription request message. The first terminal user can be a VIP user, and the first service can include the same service of one or more APPs (APPs), or the same type of service of different types of APPs. The second core network element can subscribe to quality deterioration events that occur when a VIP user uses a specific APP through this second message.

[0221] The second message includes the first information, which can be used to trigger the first core network element to perceive the first number of users.

[0222] In one example, the first piece of information is the app concurrent user count awareness reporting flag (appConcurrentUserNumFlag). In other words, the app concurrent user count awareness reporting flag is extended in Nupf_EventExposure_Subscribe. After the first core network element detects this first piece of information, it can be aware of the app and thus obtain the number of users (i.e., concurrent users) using the app simultaneously from the same terminal user.

[0223] For example, the service operation name for this second message is: Nupf_EventExposure_Subscribe.

[0224] This service can be described as follows: Network function (NF) service users can subscribe to device-level event information from the first core network element through this service.

[0225] The format of the second message is as follows, and the input parameters of the second message include: required input parameters and optional input parameters.

[0226] Required input parameters include: NF identifier, event list, notification target address (notification association identifier), and event notification information.

[0227] Optional input parameters include: event-related filtering conditions, subscription association identifier, subscription expiry time, data network name (DNN), single network slice selection assistance information (S-NSSAI), data network access identifier (DNAI), UPF event openness, and APP concurrent user number awareness reporting identifier (i.e., an example of the first information), etc.

[0228] The output parameters of this second message include: required output parameters and optional output parameters.

[0229] Required output parameters: If the subscription request is acceptable, return the subscription association identifier and the subscription expiry time (expiry).

[0230] Optional output parameter: First relevant event report (if available).

[0231] For example, if a poor-quality event that meets the conditions exists after the first core network element receives the subscription request (e.g., historical data that has not been reported before or an event that is triggered in real time), the first event report can be attached to the first response message in step 504 described below.

[0232] It is understandable that, based on the input parameters of the second message, the relevant content of the subscription request from the second core network element can be clearly defined. Correspondingly, based on the output parameters of the second message, the activation of the subscription request based on the second message can be determined.

[0233] For example, the APP concurrent user count awareness reporting identifier field (i.e., the first information field) can be extended within Nupf_EventExposure_Subscribe using the definitions in Tables 1 to 4 below.

[0234] As shown in Table 1, the CreateEventSubscription type is defined, and Nupf_EventExposure_Subscribe includes the CreateEventSubscription field.

[0235] The CreateEventSubscription field includes two fields: subscription and supportedFeatures. The subscription field is of data type UPF event subscription (UpfEventSubscription).

[0236] Table 1 Definition of CreateEventSubscription type

[0237]

[0238] As shown in Table 2, the UpfEventSubscription type in Table 1 is defined. The UpfEventSubscription field includes an event list field, and the data type of the event list field is an array (Upf event (UpfEvent)).

[0239] Table 2 Definition of UpfEventSubscription type

[0240]

[0241] As shown in Table 3, the UpfEvent type is defined in Table 2. The UpfEvent field includes the reportingSuggestionInfo field.

[0242] The data type of the reportingSuggestionInfo field is ReportingSuggestionInformation.

[0243] Table 3 Definition of UpfEvent type

[0244]

[0245] As shown in Table 4, the ReportingSuggestionInformation type in Table 3 is defined. The ReportingSuggestionInformation field includes the APP concurrent user count identifier (appConcurrentUserNumFlag) field, and the data type of the appConcurrentUserNumFlag field is the APP concurrent user count identifier (APPConcurrentUserNumFlag).

[0246] Table 4 Definitions of ReportingSuggestionInformation Types

[0247]

[0248] It is understood that Tables 2 and 3 are merely examples. Optionally, the definitions in Tables 2 and 3 may also include descriptions of the applicability of each attribute, which is not limited in this embodiment of the application.

[0249] For details regarding the definitions of the Nupf_EventExposure_Subscribe fields in Tables 1 to 4, please refer to the detailed content in 3GPP TS 23.502 V19.3.0 (2025-03), which will not be repeated here.

[0250] In step 502, the second core network element sends the second message. Correspondingly, the first core network element receives the second message.

[0251] For example, the second core network element can send the second message through the Nupf interface. Correspondingly, the first core network element can receive the second message based on the Nupf interface.

[0252] In step 503, the first core network element determines the number of first users based on the characteristic information of the first service of the first terminal user. The number of first users is the number of users who use the first service simultaneously.

[0253] For example, after receiving the second message, the first core network element can determine the number of first users based on the first information included in the second message and the characteristic information of the first service of the first terminal user; or, the first core network element can determine the number of first users based on the characteristic information of the first service of the first terminal user, according to a local configuration. This local configuration is used to configure the first core network element to perceive the number of users simultaneously using the first service.

[0254] One possible implementation is that the first core network element determines the number of first users based on the first information in the second message and the characteristic information of the first service of the first terminal user, wherein the first information triggers the first core network element to perceive the number of users using the first service simultaneously.

[0255] For example, the first information is the APP concurrent user count awareness and reporting identifier, the first service is the first APP, and after the first core network element receives the second message, it can detect the first information carried in the second message (i.e., the APP concurrent user count identifier), thereby enabling the first core network element to have the APP concurrent user count awareness capability. Based on the APP concurrent user count awareness capability, and at least one of the following characteristics: the number of concurrent streams accessing the APP by users within a period (e.g., 5 seconds), the start and end time of each stream in the concurrent stream, the temporal relationship between different streams in the concurrent stream, traffic statistics information, and uplink and downlink packets or rates, it can perform real-time awareness through an AI model to obtain the first user count (i.e., the APP concurrent user count).

[0256] In other words, once the first core network element detects the first information included in the second message, it can trigger the sensing of the number of users simultaneously using the first service.

[0257] For details regarding the determination of the number of first users by the first core network element based on the characteristic information of the first service of the first terminal user, please refer to step 410 of method 400. It will not be repeated here.

[0258] One possible implementation is that the first core network element takes effect according to its local configuration, and determines the number of first users based on the characteristic information of the first service of the first terminal user. The local configuration is used to configure the first core network element to sense the number of users using the first service at the same time.

[0259] For example, the first core network element can be locally configured to perceive the number of users simultaneously using the first service. When this local configuration is effective, the first core network element can determine the number of first users based on the characteristic information of the first service of the first terminal user.

[0260] In other words, the first core network element can locally configure the capability related to the number of users simultaneously using the first service. Once this capability is enabled, the number of users can be obtained through sensing without needing to extend the first information in the second message sent by the second core network element. This reduces signaling overhead.

[0261] For details regarding the determination of the number of first users by the first core network element based on the characteristic information of the first service of the first terminal user, please refer to step 410 of method 400. It will not be repeated here.

[0262] In step 504, the first core network element sends a first response message. Correspondingly, the second core network element receives the first response message.

[0263] For example, the aforementioned second message is a VIP user APPs poor quality event subscription request message. Correspondingly, the first response message could be, for example, a VIP user APPs poor quality event subscription response message. That is, in response to the second message, the first core network element sends the first response message to the second core network element.

[0264] Based on the first response message, the first core network element can confirm with the second core network element that the subscription relationship has been successfully established, and inform the second core network element that the subscription for the VIP user whose quality issues occurred while using a specific APP has been accepted.

[0265] In step 505, the first core network element determines the QoE result and / or the quality difference result based on the first number of users.

[0266] For example, after determining the first number of users based on the first core network element in step 503 above, the method may optionally further include: the first core network element determining the quality difference result and / or QoE result based on a first algorithm, wherein the input parameters of the first algorithm include the first number of users.

[0267] The first algorithm can be a QoE algorithm (or model) and / or a quality defect judgment algorithm (or model). The QoE algorithm can be used to obtain QoE results, and the quality defect judgment algorithm can be used to obtain quality defect results.

[0268] For example, parameters related to the number of first users can be recalculated based on the number of single users. The recalculated parameters can then be used as input parameters to the QoE algorithm and / or the quality difference judgment algorithm to determine the quality difference result and / or the QoE result, thereby enhancing the QoE algorithm and / or the quality difference judgment algorithm.

[0269] The method for calculating based on the number of users can be, for example, by calculating the average, weighted average, median, etc., and this application does not limit this method.

[0270] Taking the calculation of the average value as an example, when the number of the first users is n, the parameters related to the number of the first users may include, for example, the n bandwidths, n delays, n rates, etc. corresponding to the n users. This application does not limit this.

[0271] By calculating the average of these n bandwidths, the bandwidths corresponding to these n users are converted into the bandwidth corresponding to a single user.

[0272] Similarly, by calculating the average of these n delays, the n delays corresponding to these n users are converted into the delay corresponding to a single user.

[0273] Similarly, by calculating the average of the n rates, the n rates corresponding to the n users are converted into the rate corresponding to a single user.

[0274] It is understood that the above method of calculating the average value to convert the relevant parameters corresponding to n users into the relevant parameters corresponding to a single user is merely an example and should not constitute any limitation on the embodiments of this application.

[0275] In another example, the number of first users is set as the feature information, which can be the annotation information. Then, the number of first users is used as the input parameter to the QoE algorithm and / or the quality difference judgment algorithm, thereby enhancing the QoE algorithm and / or the quality difference judgment algorithm.

[0276] In other words, when extracting feature and annotation information during QoE evaluation, the first user count is input as new feature information into the first algorithm. This is used to characterize that the multiple sets of feature information obtained by the first core network element through sensing are based on the same service. This ensures that during model training, each sample adds the concurrent user count feature to the original collected service flow features, and that the concurrent user count is appropriately processed during subsequent token and vectorization processes.

[0277] Optionally, the first core network element can adjust the first algorithm based on the first number of users. In this way, the first core network element can obtain accurate QoE results and / or poor quality results based on the adjusted first algorithm. The first algorithm can also be an AI model, etc., and this application embodiment does not limit this.

[0278] In other words, once the first core network element determines its ability to sense the number of users simultaneously using the first service, it obtains this number through sensing and can then adjust the QoE algorithm and / or the quality difference assessment algorithm. This allows the QoE algorithm and / or quality difference assessment algorithm to also support extended multi-user concurrent scenarios in mobile applications.

[0279] Figure 6This is a diagram of the QoE and / or quality degradation assessment algorithm architecture provided in the embodiments of this application. The QoE and / or quality degradation assessment algorithm architecture includes the following module: live network traffic, service awareness (SA) identification, KPI statistics, service KQI model, and QoE scoring.

[0280] Among them, the current network traffic is used to monitor real-time bandwidth utilization and determine whether the current communication is congested or idle.

[0281] SA (Service Provider) identification: Used to identify different service types in the network. For example, it may include the aforementioned first service.

[0282] KPI statistics: can be used to collect characteristic information of the aforementioned first business.

[0283] One possibility is that the feature information may include: uplink rate, downlink rate, uplink round-trip time (RTT), downlink RTT, jitter, packet loss rate, etc. This feature information may be obtained by adjusting for the number of users mentioned above.

[0284] One possible scenario is that the feature information could include: uplink rate, downlink rate, uplink round-trip time (RTT), downlink RTT, jitter, packet loss rate, and the number of first users, etc. The number of first users can then be used as new feature information input into the model for training.

[0285] The above parameters are used as input parameters to input the key quality indicator (KQI) model (or algorithm), which is an example of the first algorithm mentioned above.

[0286] The KQI model primarily outputs QoE results through AI models (or algorithms), mathematical modeling, and rule mapping. AI models can be, for example, Transformer models and multi-layer perceptrons (MLPs). Mathematical modeling can include regression models, sequence models, and so on. Rule mapping can include mathematical rules (e.g., addition, subtraction, multiplication, division, weighting), mathematical formulas, and so on.

[0287] The business KQI model can output QoE results. Taking the first business as a live streaming business as an example, the QoE result may include, but is not limited to, at least one of the following parameters: bit rate, stutter rate, stutter duration, initial buffer duration, etc.

[0288] Furthermore, QoE scoring can be performed based on the QoE results output by the business KQI model.

[0289] It is understood that obtaining accurate QoE results and / or poor quality results based on the above two methods is merely an example, but the scope of protection of this application is not limited thereto. Any person skilled in the art can easily conceive of variations or substitutions within the scope of the technology disclosed in this application, or other messages and processes that can achieve accurate QoE results and / or poor quality results in multi-user concurrent scenarios of an APP, all of which fall within the scope of this patent.

[0290] Furthermore, the first core network element can use the first number of users as the input parameter of the adjusted first algorithm, and determine the quality difference result and / or QoE result through training.

[0291] In step 506, the first core network element sends a first message #1, which includes the first number of users and / or the guaranteed bandwidth of the first service, which is determined based on the first number of users.

[0292] Accordingly, the second core network element receives the first message #1.

[0293] It can be understood that this first message #1 is an example of the first message in the aforementioned method 400. For details regarding the first message #1, please refer to the detailed content of the first message in the aforementioned method 400, which will not be repeated here.

[0294] Taking the second message in step 501 as a VIP user APPs poor quality event subscription request message as an example, the corresponding first message #1 could be a VIP user APPs poor quality event notification message (for example, it could be a Nupf_EventExposure_Notify message).

[0295] One possibility is that the first message #1 includes the first number of users.

[0296] After receiving the first message #1, the second core network element can further determine the guaranteed bandwidth required for the first service based on the first number of users included in the first message #1.

[0297] For example, the service operation name of the first message #1 is: Nupf_EventExposure_Notify. This service can be described as follows: When an event subscribed to by the second core network element of the NF service consumer occurs, the first core network element notifies the second core network element of one or more PDU session-related event information through this service.

[0298] The format of the first message #1 is as follows. The input parameters of the first message #1 include: required input parameters and optional input parameters.

[0299] Required input parameters include: event ID, UE address (i.e., IP address), and notification association ID.

[0300] Optional input parameters include: UE ID, event-specific parameters, policy timestamp, application ID, and stream filtering conditions.

[0301] The output parameters for the first message #1 include: required output parameters and optional output parameters.

[0302] Required output parameter: result indicator (or result identifier).

[0303] For example, after receiving the first message #1, the second core network element can return a processing result identifier (e.g., "successfully received", or "repeatedly reported", etc.) to the first core network element to inform whether the first message #1 reported this time has been processed normally.

[0304] Optional output parameters: None. That is, there are no optional output parameters.

[0305] It is understandable that the input parameters of the first message #1 can ensure that the event is traceable, and so on.

[0306] Accordingly, the output parameters of the first message #1 can be used to feed back the processing result of the first message #1, thereby improving the reliability of the first message #1 reporting process.

[0307] For example, the first user digital segment that is used by the first terminal user simultaneously using the first service can be extended within Nupf_EventExposure_Notify by the definitions in Tables 5 to 9 below.

[0308] As shown in Table 5, the NotificationData type definition, Nupf_EventExposure_Notify includes a NotificationData field, which consists of two fields: notificationItems and correlationId. The data type of notificationItems is an array (array(NotificationItem)).

[0309] Table 5 Definition of NotificationData type

[0310]

[0311] As shown in Table 6, the NotificationItem type is defined in Table 5. The NotificationItem field includes the qosAnaInfo field, and the data type of the qosAnaInfo field is QosAnalysisInfo.

[0312] Table 6 Definition of NotificationItem type

[0313]

[0314] As shown in Table 7, the QosAnalysisInfo type is defined in Table 6. The QosAnalysisInfo field includes the infoIndicate field, and the data type of the infoIndicate field is QosInfoType.

[0315] Table 7 Definition of QosAnalysisInfo type

[0316]

[0317] As shown in Table 8, the QosInfoType parameter is defined in Table 7. The QosInfoType field includes the infoIndicate field, and the data type of the infoIndicate field is QosInfoType.

[0318] Table 8 QosInfoType parameter definition

[0319]

[0320] As shown in Table 9, the QosMonitoringReport type is defined in Table 7. The QosMonitoringReport field includes the APP concurrent user count (appConcurrentUserNum) field, and the data type of the appConcurrentUserNum field is integer.

[0321] Table 9 Definition of QosMonitoringReport Type

[0322]

[0323] As can be seen, appConcurrentUserNum is an optional input parameter. The base of appConcurrentUserNum is 0 to 1, and appConcurrentUserNum represents the number of concurrent users of the APP (that is, the first user).

[0324] It is understood that Tables 5, 7 and 9 are merely examples. Optionally, the definitions of Tables 5, 7 and 9 may also include descriptions of the applicability of each attribute, which is not limited in this embodiment of the application.

[0325] For details regarding the definitions of the Nupf_EventExposure_Notify fields in Tables 5 to 9, please refer to the detailed content in 3GPP TS 23.502 V19.3.0 (2025-03), which will not be repeated here.

[0326] One possibility is that the first message #1 includes the guaranteed bandwidth for the first service.

[0327] In other words, after the first core network element determines the first number of users, it can further determine the guaranteed bandwidth for simultaneous use of the first service by the first terminal user based on this first number of users and the guaranteed bandwidth for a single user using the first service. That is, it can be determined that when multiple users access the first service simultaneously, the bandwidth that ensures a good user experience for the first service can be guaranteed.

[0328] In other words, the first core network element can directly send the guaranteed bandwidth required for the first service under the first number of users to the second core network element through the first message #1. In this case, the second core network element does not need to calculate the guaranteed bandwidth required for the first service under the first number of users.

[0329] One possibility is that the first message #1 includes the first number of users and the guaranteed bandwidth for the first service.

[0330] That is, after determining the first number of users, the first core network element can further determine the guaranteed bandwidth for simultaneous use of the first service by the first terminal user based on the first number of users and the guaranteed bandwidth for a single user using the first service. Furthermore, the first core network element can report the determined first number of users and the guaranteed bandwidth for the first service to the second core network element via the first message #1.

[0331] After determining the first number of users based on the first core network element in step 503 above, the method may optionally further include: the first core network element determining the quality difference result and / or QoE result based on a first algorithm, wherein the input parameters of the first algorithm include the first number of users.

[0332] For example, the first core network element can determine the quality difference result and / or QoE result based on the first algorithm adjusted in step 505 above.

[0333] For details regarding the first algorithm and the first core network element obtaining the quality difference result and / or QoE result based on the first algorithm, please refer to the detailed content in step 505 of method 500, which will not be repeated here.

[0334] Optionally, the second message is a quality-poor subscription request message. In this case, the first message #1 also includes second information characterizing the quality-poor result and / or QoE result, the second information being determined based on the first number of users.

[0335] The first core network element can report the second information used to characterize the determined quality difference result and / or QoE result to the second core network element through the first message #1.

[0336] For example, as mentioned above, Table 8 defines the QosInfoType parameter, which includes Quality of Service Analysis (QOS_ANA). QOS_ANA indicates that Quality of Service Analysis Information (QosAnalysisInfo) is used for poor quality information, or in other words, for ensuring the quality of service experience.

[0337] This second piece of information could be, for example, the QosInfoType field in Table 8, where the QosInfoType field takes the value QOS_ANA.

[0338] Optionally, the first core network element sends the first message #1, which includes: the first core network element sends the first message #1 when the number of users of the first terminal user using the first service at the same time changes.

[0339] That is, the first message is also used to indicate that the number of users of the first account using the first service at the same time has changed.

[0340] The first core network element can continuously monitor the number of users simultaneously using the first service. When the first core network element determines through sensing that the characteristic information of the first terminal user using the first service has changed, it can determine that the number of users simultaneously using the first service through the first terminal user has changed. In this case, the first core network element can be triggered to send the first message #1 to the second core network element.

[0341] For example, the first core network element can further determine the first number of users based on the acquired feature information of the first service using an AI model or algorithm. Then, the first core network element reports this first number of users to the second core network element via the first message #1.

[0342] Optionally, the sending of the first message #1 by the first core network element further includes: when a poor quality event occurs, triggering the first core network element to report the first message #1 to the second core network element.

[0343] As mentioned earlier, the second message is a subscription request message for VIP user APPs poor quality events. Therefore, when a poor quality event occurs, the first core network element can be triggered to report the first message #1 to the second core network element.

[0344] In step 507, the second core network element determines the guaranteed bandwidth for the first service.

[0345] One possibility is that the first message #1 includes the first user count.

[0346] Optionally, the method further includes: the second core network element determining the guaranteed bandwidth for the first service based on the first number of users.

[0347] For example, the second core network element can obtain the guaranteed bandwidth of the first service when multiple users are using the first service, based on the first number of users and the guaranteed bandwidth when a single terminal user uses the first service.

[0348] For example, the guaranteed bandwidth of the first service can satisfy the following condition: the guaranteed bandwidth of the first service is equal to the number of first users n multiplied by the guaranteed bandwidth when a single user uses the first service.

[0349] In this way, the second core network element can increase its computing power based on the number of first users when calculating the guaranteed bandwidth, thereby providing the necessary effective bandwidth guarantee for multiple users who simultaneously use the first service through the first terminal user.

[0350] One possibility is that the first message #1 includes the guaranteed bandwidth for the first service.

[0351] For example, the second core network element can directly obtain the guaranteed bandwidth for the current multi-user use of the first service based on the first message #1. Thus, the second core network element does not need to calculate the guaranteed bandwidth for the first service based on the number of first users, thereby reducing the computational overhead of the second core network element.

[0352] It is understood that the second core network element obtains the guaranteed bandwidth of the first service based on the first message reported by the first core network element. This is just an example. Other messages and processes that can achieve accurate guaranteed bandwidth calculation are within the scope of this patent.

[0353] Optionally, the method further includes: the second core network element determining the ABR based on the first number of users.

[0354] When the number of users simultaneously using the first service through the first terminal user is equal to the number of users n, a multiple of the number of users can be introduced for processing. For example, the ABR corresponding to the first service can satisfy: the ABR corresponding to the first service is equal to n multiplied by the ABR corresponding to a single user using the first service.

[0355] In step 508, the second core network element sends a PCF policy recommendation request message #1. This PCF policy recommendation request message #1 can carry the first recommended bandwidth for the first service, which is the guaranteed bandwidth for the first service. Correspondingly, the PCF receives the PCF policy recommendation request message #1.

[0356] After the second core network element determines the guaranteed bandwidth for the first service, it can push policy adjustment suggestions to the PCF based on the guaranteed bandwidth.

[0357] For example, the second core network element sends a PCF policy recommendation request message #1, and then the PCF can trigger the establishment of a dedicated carrier based on the first recommended bandwidth of the first service carried in the PCF policy recommendation request message #1.

[0358] In step 509, the PCF establishes a GBR dedicated carrier based on the PCF policy recommendation request message.

[0359] PCF can trigger dedicated load creation based on the first recommended bandwidth carried in the PCF policy recommendation request message for the first service; or, in other words, PCF can request GBR bandwidth according to the first recommended bandwidth when creating a dedicated load. This GBR bandwidth is also the first recommended bandwidth, and it satisfies the following condition: the GBR bandwidth equals the number of first users n multiplied by the guaranteed bandwidth for a single user using the first service. In other words, PCF can request GBR bandwidth according to the number of first users n when creating a dedicated load.

[0360] In step 510, the PCF sends a PCF policy recommendation notification message. Correspondingly, the second core network element receives this PCF policy recommendation notification message.

[0361] PCF can generate policies based on real-time or historical decision results, and send the generated policies to the second core network elements through PCF policy recommendation notification messages.

[0362] In step 511, the second core network element calculates the available resource data of the access network device based on the tag established by the dedicated carrier.

[0363] For example, the tags established by the dedicated network may include service type identifiers, QoS parameter associations, or resource occupancy records, etc. The second core network element can calculate and obtain the available resources of the access network device based on the above tags.

[0364] In step 512, if the number of users simultaneously using the first service by the first terminal user changes, the first core network element determines the second number of users and / or the guaranteed bandwidth of the first service, which is determined based on the second number of users.

[0365] The number of first users simultaneously using the first service through the first terminal user may change over time. For example, the number of first users may increase or decrease.

[0366] For example, a first core network element can continuously monitor the number of first users simultaneously using the first service. When the first core network element determines through sensing that the characteristic information of the first terminal user using the first service has changed, it can determine that the number of first users simultaneously using the first service through the first terminal user has changed. Based on this, the first core network element can further determine the number of second users based on the acquired characteristic information of the first service, using an AI model or algorithm.

[0367] The second user count is another example of the aforementioned first user count. For details regarding how the first core network element obtains the second user count based on the characteristic information of the first service, please refer to the detailed explanation of how the first core network element obtains the first user count in method 400; it will not be repeated here.

[0368] Optionally, the first core network element can also continuously monitor the poor-quality service flow of the first service. When the first core network element determines that the poor-quality service flow of the first service has changed, it can determine that the number of users simultaneously using the first service through the first terminal user may have changed. Based on this, the first core network element can further determine the number of second users based on the acquired feature information of the first service, using an AI model or algorithm.

[0369] It is understood that the first number of users and the second number of users may be the same or different, etc., and this application embodiment does not limit this.

[0370] In step 513, the first core network element sends a first message #2, which includes a second number of users and / or a guaranteed bandwidth for the first service, the guaranteed bandwidth being determined based on the second number of users. Correspondingly, the second core network element receives the first message #2.

[0371] It is understood that the first message #2 is another example of the first message in the aforementioned method 400, and the second user count is another example of the aforementioned first user count. For details regarding the first message #2 and the second user count, please refer to the detailed content of the first message and the first user count in the aforementioned method 400, which will not be repeated here.

[0372] In step 514, the second core network element determines the guaranteed bandwidth for the first service.

[0373] In step 515, the second core network element sends a PCF policy recommendation request message #2. This PCF policy recommendation request message #2 may carry the second recommended bandwidth for the first service, which is the guaranteed bandwidth for the first service. Correspondingly, the PCF receives the PCF policy recommendation request message #2.

[0374] PCF strategy recommendation request message #2 is an example of PCF strategy recommendation request message #1 in step 508 above, and should not constitute any limitation on the embodiments of this application.

[0375] For details regarding steps 513 to 515, please refer to steps 506 to 508 of method 500; they will not be repeated here.

[0376] It should be noted that, based on the method shown in method 500, through the first core network element, the second core network element, the PCF, the AMF, and the first terminal user and the SMF (the first terminal user and the SMF are in... Figure 5 Interaction between (not shown in the image) enables VIP users to enhance their awareness and protection capabilities regarding the number of first-time users for key services.

[0377] Based on the above technical solution, the first core network element can enhance its ability to perceive the number of users simultaneously using the first service through the first terminal user (i.e., the first number of users). The information of this first number of users can be expanded in the first message reported by the first core network element, or the information of the guaranteed bandwidth of the first service obtained based on this first number of users can be expanded. This allows the second core network element to calculate the guaranteed bandwidth based on the guaranteed bandwidth of the first service carried in the first message, or based on the guaranteed bandwidth when a single user uses the first service and the first number of users, when recommending a quality assurance strategy. In this way, the experience guarantee of the first service can be ensured.

[0378] Furthermore, when the second core network element sends a second message to the first core network element, it can extend the ability to sense the number of concurrent users (i.e., the number of first users) of the first service. Before making a quality defect judgment through QoE / KPI, the first core network element adds the processing of sensing the number of first users simultaneously using the first service, and then adjusts the QoE / quality defect evaluation algorithm based on the sensed number of first users to ensure accurate quality defect results and / or QoE results are reported. In this way, operators can accurately sense the user concurrency status of the first service in the network based on this sensing function, and achieve accurate sensing, protection and management under VIP user key service protection or differentiated billing and control strategies.

[0379] Scenario 2: For experience maps, user perception analysis results, or visible assurance effects, indicators that reflect the number of concurrent users.

[0380] Figure 7 This is another illustrative flowchart of the communication method provided in the embodiments of this application. Figure 7 The method 700 shown is based on Figure 4 Based on method 400, another processing logic of the communication method is shown. Method 700 is based on method 400, and describes the method provided in this application from the perspective of interaction between a first core network element, a second core network element, a first terminal user, an SMF, a PCF, and an AMF, but this should not constitute any limitation on this application. Furthermore, Figure 7 The first core network element can also be replaced by components in the first core network element, such as chips, chip systems, processors, etc., or by logic modules or software that can realize some or all of its functions. Figure 7 The second core network element can also be replaced with components in the second core network element, such as chips, chip systems, processors, etc., or it can be replaced with logic modules or software that can realize some or all of its functions. Figure 7 The first terminal user, SMF, PCF, or AMF can also be replaced by components in the first terminal user, SMF, PCF, or AMF, such as chips, chip systems, processors, etc., or can be replaced by logic modules or software that can implement some or all of its functions, etc., which are not limited in this application.

[0381] The following text focuses on describing the steps that differ from those in Method 400. For explanations of the steps that are the same as those in Method 400, as well as the same terms, please refer to the relevant descriptions above, which will not be repeated here.

[0382] For example, the first core network element may be a UPF, the second core network element may be an NWDAF, etc., and this application embodiment does not limit this.

[0383] It should be noted that, Figure 7 The first core network element, the second core network element, the first terminal user, the SMF, the PCF, and the AMF shown are merely examples and should not constitute any limitation on the embodiments of this application.

[0384] See Figure 7 , Figure 7 The method 700 shown may include steps 701 to 710, and the steps in method 700 are described in detail below.

[0385] In step 701, the second core network element determines a second message, which includes first information. The first information is used to trigger the first core network element to perceive the first number of users, which is based on the number of users of the first terminal user who are simultaneously using the first service.

[0386] For example, the second message is a user experience document subscription request message (exemplarily, it could be a Nupf_EventExposure_Subscribe Request message), which could be, for example, a regular user experience document subscription request message.

[0387] For details regarding the first number of users, the first terminal user, and the first service, please refer to the detailed content in Method 400, which will not be repeated here.

[0388] Regarding the second message, which is a subscription request message for a general user experience, the first terminal user can be a general user, and the first service can include different apps or different types of apps. The second core network element can obtain different user service access and experience data, etc., through this second message.

[0389] The second message includes the first information, which can be used to trigger the first core network element to perceive the first number of users.

[0390] In one example, the first message is the app concurrent user count awareness reporting flag (appConcurrentUserNumFlag). In other words, the app concurrent user count awareness reporting flag can be extended in Nupf_EventExposure_Subscribe (i.e., the second message). This second message format can reuse the second message format in step 510 of method 500 when extending the app concurrent user count awareness reporting flag on the Nupf_EventExposure_Subscribe message.

[0391] For details regarding the first and second messages, please refer to the detailed explanation of step 510 in method 500, which will not be repeated here.

[0392] The second piece of information also includes the Nupf EventType field. As shown in Table 10, which enumerates EventType in Table 3, EventType can include Quality of Service Analysis (QOS_ANA) and Quality of Service Experience (QOS_EXP). Among them, QOS_ANA is used for experience analysis reporting, and QOS_EXP is used for business experience assurance.

[0393] Table 10 Enumeration of Nupf EventType

[0394]

[0395] For details regarding the enumeration fields defined in Table 10 for Nupf EventType, please refer to 3GPPTS 23.502 V19.3.0 (2025-03). Further details will not be provided here.

[0396] In step 702, the second core network element sends the second message. Correspondingly, the first core network element receives the second message.

[0397] For example, the second core network element can send the second message through the Nupf interface. Correspondingly, the first core network element can receive the second message based on the Nupf interface.

[0398] In step 703, the first core network element determines the first number of users based on the feature information of the first service of the first terminal. The first number of users is the number of users who use the first service at the same time.

[0399] In step 704, the first core network element sends a second response message. Correspondingly, the second core network element receives the second response message.

[0400] For example, the aforementioned second message is a regular user experience subscription request message. Correspondingly, the second response message could be, for example, a regular user experience subscription request response message. That is, in response to the second message, the first core network element sends the second response message to the second core network element.

[0401] In step 705, the first core network element determines the QoE result based on the first terminal user and the first number of users.

[0402] After determining the first number of users based on the first core network element in step 703 above, the method may optionally further include: the first core network element determining the QoE result based on a first algorithm, wherein the input parameters of the first algorithm include the first number of users.

[0403] For details regarding the first algorithm and the QoE results obtained by the first core network element based on the first algorithm, please refer to step 505 of method 500, which will not be repeated here.

[0404] In step 706, the first core network element sends a first message #3, which includes the first number of users and / or the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the first number of users. Correspondingly, the second core network element receives the first message #3.

[0405] Taking the second message in step 701 as a regular user experience document subscription request message as an example, the corresponding first message #3 could be, for example, a user-level experience perception information notification message.

[0406] It can be understood that this first message #3 is an example of the first message in the aforementioned method 400. The format of the first message #3 can reuse the format of the first message #1 in the aforementioned method 500, and will not be described again.

[0407] For details regarding the first message #3, please refer to the first message in method 400 and the first message #1 in method 500, which will not be repeated here.

[0408] Optionally, the second message is a user experience document subscription request message. In this case, the first message #3 also includes a QoE result, which is determined based on the first number of users.

[0409] The first core network element can report the QoE result to the second core network element through the first message #3.

[0410] For example, as mentioned above, Table 8 defines the QosInfoType parameter, which includes Quality of Service Experience (QOS_EXP). QOS_EXP indicates that Quality of Service Analysis Information (QosAnalysisInfo) is used for experience information reporting, or for experience analysis reporting.

[0411] The first message may also include, for example, the QosInfoType field in Table 8, with the value QOS_EXP.

[0412] For details regarding steps 702 to 706, please refer to the detailed content of steps 502 and 506 in the aforementioned method 500, which will not be repeated here.

[0413] In step 707, the second core network element determines at least one of the following based on the first message #3: experience map, user perception analysis results, or visual interface of protection effect.

[0414] The first message #3 carries the first number of users and the QoE result. The second core network element can generate at least one of the following based on the QoE result: an experience map, user perception analysis results, or a visual interface for guarantee effectiveness. Among these, at least one of the above can present the first number of users for each first service in different time periods.

[0415] For example, the first business is APP#1, which can be displayed on the generated experience map as the number of concurrent users accessing APP#1 at different time periods (i.e., the number of first users); as another example, it can be displayed in the generated user perception analysis results as the number of concurrent users accessing APP#1 at different time periods (i.e., the number of first users); as yet another example, it can be displayed in the generated guarantee effect visualization interface as the number of concurrent users accessing APP#1 at different time periods (i.e., the number of first users).

[0416] Furthermore, based on the existing statistical method, it can be determined that the number of users who simultaneously access APP#1 through the first terminal user is 1, that is, only the first terminal user is accessing APP#1, and the number of other users who simultaneously access APP#1 through the first terminal user cannot be displayed.

[0417] Therefore, when counting the number of users using APP#1, the counting method can be modified based on this first user count. For example, this first user count can be used to determine the number of users who simultaneously access APP#1 through the first terminal user.

[0418] In this way, when operators view the APP experience analysis map, APP user perception analysis results, or APP guarantee effect analysis reports and other externally presented views or data, they can see the precise number of concurrent users (i.e., the number of first users) of the APP in different time periods in the network, so as to guide the next step of network optimization, package design, etc.

[0419] In step 708, if the number of users simultaneously using the first service by the first terminal user changes, the first core network element determines the second number of users and / or the guaranteed bandwidth of the first service, which is determined based on the second number of users.

[0420] In step 709, the first core network element sends a first message #4, which includes the second number of users and / or the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the second number of users. Correspondingly, the second core network element receives the first message #4.

[0421] It can be understood that the first message #4 is an example of the first message in method 400 or the first message #3 in method 700. For details regarding the first message #1, please refer to the detailed content of the first message in method 400 or the first message #3 in method 700, which will not be repeated here.

[0422] For details regarding steps 708 and 709, please refer to steps 512 and 513 of the aforementioned method 500; they will not be repeated here.

[0423] In step 710, the second core network element determines at least one of the following based on the first message #4: experience map, user perception analysis results, or visual interface of protection effect.

[0424] For details regarding step 710, please refer to step 707 of the aforementioned method 700; further explanation is not required here.

[0425] It should be noted that, based on the method shown in method 700, through the first core network element, the second core network element, the AMF, and a terminal user, the SMF, and the PCF (the first terminal user, the SMF, and the PCF are in... Figure 7 Interactions between (not shown in the image) and the experience map, user perception analysis results, or visual interfaces for assurance effectiveness can enhance the perception and assurance capabilities of the first number of users for the first business.

[0426] Based on the above technical solution, the first core network element can enhance its ability to perceive the number of users simultaneously using the first service through the first terminal user (i.e., the first number of users). The information of this first number of users can be expanded in the first message reported by the first core network element, or the information of the guaranteed bandwidth of the first service obtained based on this first number of users can be expanded. This allows the second core network element to calculate the guaranteed bandwidth based on the guaranteed bandwidth of the first service carried in the first message, or based on the guaranteed bandwidth when a single user uses the first service and the first number of users, when recommending a quality assurance strategy. In this way, the experience guarantee of the first service can be ensured.

[0427] Furthermore, when the second core network element sends the second message to the first core network element, it can extend the ability to perceive the number of concurrent users (i.e., the number of first users) of the first service. Before obtaining the QoE result through the QoE algorithm or model, the first core network element adds the perception processing of the number of first users using the first service at the same time, and then adjusts the QoE evaluation algorithm based on the perceived number of first users to ensure that accurate QoE results are obtained and reported.

[0428] Furthermore, based on the ability of the first core network element to perceive the number of first users simultaneously using the first service, the second core network element or report can present the number of first users accessing the first service and experience data collected by the second core network element on the first core network element. This can generate experience maps, assurance effect analysis reports, or assurance effect visualization interfaces for external presentation, thereby reflecting the accurate number of first users simultaneously using the first service in different time periods in the network, so as to guide the next step of network optimization, package design, etc.

[0429] Scenario 3: For PCC content billing and control solutions, implement business processes that perceive and differentiate strategies and billing controls for different numbers of concurrent users.

[0430] Figure 8 This is another illustrative flowchart of the communication method provided in the embodiments of this application. Figure 8 The method 800 shown is based on Figure 4 Based on method 400, another processing logic of the communication method is shown. Method 800 is based on method 400, and describes the method provided in this application from the perspective of the interaction between the first core network element, NWDAF, first terminal user, SMF, PCF, and AMF, but this should not constitute any limitation on this application. Furthermore, Figure 8 The first core network element can also be replaced by components in the first core network element, such as chips, chip systems, processors, etc., or by logic modules or software that can realize some or all of its functions. Figure 8 The NWDAF, first terminal user, SMF, PCF or AMF in the application can be replaced with components in the NWDAF, first terminal user, SMF, PCF or AMF, such as chips, chip systems, processors, etc., or can be replaced with logic modules or software that can implement some or all of their functions. This application does not limit this.

[0431] The first core network element can be, for example, a UPF, an SMF, or a PCF, which can be referred to as the second core network element, etc. This application does not limit this.

[0432] See Figure 8 , Figure 8 The method 800 shown may include steps 801 to 811, and the steps in method 800 are described in detail below.

[0433] In step 801, the first terminal user sends a user session establishment / update message. Correspondingly, the SMF receives the user session establishment / update message.

[0434] In step 802, the SMF determines the SM policy control creation request message.

[0435] For example, the SM policy control creation request message can be an Npcf_SMPolicyControl CreateRequest message.

[0436] In step 803, the SMF sends the SM policy control creation request message. Correspondingly, the PCF receives the SM policy control creation request message.

[0437] For example, the SM policy control creation request message can be a request for session-related policies from the PCF through the Npcf_SMPolicyControlCreate Request service interface.

[0438] In step 804, the PCF determines a third message, which includes first information. The first information is used to trigger the first core network element to perceive the first user count, which is based on the number of users of the first terminal user who are simultaneously using the first service.

[0439] It is understood that the third message is the same as the second message in the aforementioned methods 500 and 700, and is an example of the second message, and should not constitute any limitation on the embodiments of this application.

[0440] In this case, the PCF can be referred to as the second core network element. That is, the second core network element is the PCF.

[0441] Optionally, step 804 can be replaced by: the second core network element determining a second message, the second message including first information, the first information being used to trigger the first core network element to perceive the first number of users, the first number of users being based on the number of users of the first terminal user simultaneously using the first service.

[0442] For details regarding the second or third message, please refer to the methods 500 and 700 for the specific content of the second message; further details will not be provided here.

[0443] For example, the second message (i.e., the third message) may be an SM policy control create response (for example, an Npcf_SMPolicyControl Create Response message), which includes the first information.

[0444] One possibility is that the first piece of information is the app concurrent user count awareness reporting identifier (appConcurrentUserNumFlag).

[0445] That is, the SM policy control creation response determined by PCF adds an APP concurrent user number awareness and reporting identifier field to activate the awareness function of the number of users using the first service at the same time on the first core network element.

[0446] For details regarding the first piece of information being the APP concurrent user count reporting identifier, please refer to step 501 of method 500 for the detailed information on the first piece of information, which will not be repeated here.

[0447] One possibility is that the first information includes policy and billing control matching rules, in which the number of at least one candidate user using the first service simultaneously corresponds one-to-one with at least one policy and billing control.

[0448] That is, the SM policy control creation response determined by PCF includes policy and charging control matching rules. In these policy and charging control matching rules, the APP identifier (APPId) can be used as a dynamic matching rule condition. The APPId is used to uniquely identify different APPs.

[0449] For example, in the policy and billing control matching rules, "APPId=1" corresponds to policy and billing control #1; "APPId=2" corresponds to policy and billing control #2.

[0450] Furthermore, the number of at least one candidate user simultaneously using the first service can be added as a dynamic rule matching condition.

[0451] For example, in this policy and billing control matching rule, "APPId=1" and the number of candidate users using the first service at the same time is n1, which corresponds to policy and billing control #1; "APPId=1" and the number of candidate users using the first service at the same time is n2, which corresponds to policy and billing control #2; "APPId=2" and the number of candidate users using the first service at the same time is n3, which corresponds to policy and billing control #3.

[0452] In this way, differentiated strategies and billing controls can be implemented for different numbers of concurrent users (i.e., the first number of users) of different apps, thereby enabling differentiated management.

[0453] In step 805, the PCF sends the third message. Accordingly, the SMF receives the third message.

[0454] The PCF can send the third message to the SMF via the N7 interface. Correspondingly, the SMF can receive the third message via the N7 interface, which includes the aforementioned first information.

[0455] In step 806, the SMF determines a second message, which includes first information. The first information is used to trigger the first core network element to perceive the first number of users. The first number of users is based on the number of users of the first terminal user who are simultaneously using the first service.

[0456] For example, the second message is a session establishment request message.

[0457] It is understood that this second message is the same as the second message in methods 500 and 700 mentioned above. For details, please refer to the detailed description of the second message in methods 500 and 700, which will not be repeated here.

[0458] Optionally, the SMF can be referred to as the second core network element. That is, the second core network element is the SMF.

[0459] Based on this, step 806 can be replaced by: the second core network element determines the second message, the second message including the first information, the first information being used to trigger the first core network element to perceive the first number of users, the first number of users being based on the number of users of the first terminal user simultaneously using the first service.

[0460] For details regarding the second message, please refer to Method 500 and Method 700 for the specific content of the second message; further details will not be provided here.

[0461] For example, the second message (i.e., the third message) may be a session establishment / update message (for example, an N4 Session Establishment Request message).

[0462] Optionally, the second message includes first information, which includes policy and charging control matching rules, wherein the number of at least one candidate user using the first service simultaneously corresponds one-to-one with at least one policy and charging control.

[0463] For details regarding the first information, please refer to the detailed explanation of the first information in step 804 of method 800, which will not be repeated here.

[0464] In step 807, the SMF sends the second message. Correspondingly, the first core network element receives the second message.

[0465] The SMF can send the second message to the first core network element via the N4 interface. Correspondingly, the first core network element can receive the second message via the N4 interface.

[0466] In step 808, the first core network element determines the number of first users based on the characteristic information of the first service of the first terminal user. The number of first users is the number of users who use the first service simultaneously.

[0467] In step 809, the first core network element determines the first policy and billing control based on the first number of users.

[0468] For details regarding steps 808 to 809, please refer to steps 503 and 505 in method 500; they will not be repeated here.

[0469] Optionally, the method further includes: a first core network element determining a first policy and charging control based on the first number of users, wherein the first policy and charging control is the policy and charging control corresponding to the first number of users in the policy and charging control matching rules.

[0470] For example, the APPId used to identify the first service is m, the number of the first users is n, in the policy and billing control matching rules, "APPId=m", and the number of candidate users using the first service at the same time is n, corresponding to the first policy and billing control.

[0471] The first core network element can determine the policy and charging control corresponding to the first number of users as the first policy and charging control by using the correspondence in the policy and charging control matching rules, based on the first number of users being n.

[0472] In step 810, the first core network element determines the guaranteed bandwidth and / or ABR for the first service based on the first number of users.

[0473] For details regarding the determination of the guaranteed bandwidth of the first service by the first core network element based on the first number of users in step 810, please refer to the detailed content of step 420 in method 400 or step 506 in method 500, which will not be repeated here.

[0474] For details regarding the determination of the ABR by the first core network element based on the first number of users in step 810, please refer to the detailed content of step 507 in method 500, which will not be repeated here.

[0475] In step 811, the first core network element sends a first message, which includes the guaranteed bandwidth for the first service, and the guaranteed bandwidth is determined based on the number of the first users. Correspondingly, the PCF receives the first message.

[0476] After receiving the first message, PCF can apply for GBR bandwidth based on the guaranteed bandwidth of the first service included in the first message, or in other words, based on the number of the first users, in the scenario that triggers the creation of a dedicated load.

[0477] It should be noted that, based on the method shown in method 800, through the first core network element, the first terminal user, SMF, PCF, and NWDAF, AMF (NWDAF, AMF in... Figure 8 Interaction between (not shown in the text) and key business management, enhancing the ability to perceive and manage the number of first users in the first business.

[0478] Based on the above technical solutions, operators can customize packages by defining a list of key apps that can be used by multiple concurrent users and consume a lot of wireless resources. This allows for differentiated management or billing strategies under different concurrent user specifications for each app, bringing new package revenue to operators or reducing the consumption of such users or wireless resources.

[0479] It should be understood that the steps provided in methods 400, 500, 700 and 800 above, and the execution order between each step, are merely examples and should not constitute any limitation on the embodiments of this application.

[0480] It should also be understood that, apart from the interactive architecture and processes provided in Methods 400, 500, 700 and 800 above, which extend the perception of APP concurrent users and differentiated strategies under the 5G or 5.5G network architecture for VIP users' key business protection, experience map / protection effect visualization, key business concurrency control or billing, other related functional entities, processes and solutions that can realize differentiated statistics, billing, control, protection, optimization and other functions based on APP concurrent users are all within the scope of this patent.

[0481] Figure 9 This is another schematic diagram of a network system architecture provided in the embodiments of this application. It can be seen that, compared with... Figure 1 The differences in the network system architecture shown are as follows: PCF can add the function of issuing concurrent user control policies for APPA; UPF (e.g., PDU Session Anchor UPF 1, PSA-UPF1) can add the functions of service awareness, APP concurrent user identification, and quality defect awareness, as well as the function of APP concurrent user control, and can also report the number of APP concurrent users and evaluate and optimize QoE results and / or quality defect results; NWDAF can add the functions of recommending quality defect guarantee policies and calculating guarantee bandwidth, as well as the function of visualizing QoE results and / or quality defect results under multi-service concurrency.

[0482] It is understood that the main deployment form of the method provided in this application embodiment may be to enhance the perception capability of the number of first users (or the number of concurrent users of the APP) of different types of first services on UPF, and then extend the support for the perception and control capability of the number of first users of the first service to solutions such as key service protection scenarios, experience map / protection effect visualization, key service concurrency control or billing. That is, the perception and strategy of the number of concurrent users of the APP can be presented in the corresponding interface definition, configuration data, and solution materials.

[0483] The ability to detect concurrent users of an app can be defined on the UPF, and this detection capability can also be controlled or described in the network element configuration or function description in the product manual. This is a primary method for obtaining evidence of infringement. Additionally, the ability to detect concurrent users of an app can also be described in the description of the VIP user key service protection plan or visualization function on NWDAF or other data analysis and visualization network elements. In the field of operator network equipment, evidence of infringement can also be obtained through product manuals, solution materials, and the interface definitions and interaction messages between UPF and NWDAF or other peripheral network elements.

[0484] The methods provided in the embodiments of this application have been described in detail above with reference to several accompanying drawings. The apparatus provided in the embodiments of this application will now be described with reference to the accompanying drawings.

[0485] Figures 10 to 11 These are schematic block diagrams illustrating possible apparatuses provided for embodiments of this application. These apparatuses can be used to implement the functions of the first core network element or the second core network element in the above method embodiments, and thus also achieve the beneficial effects of the above method embodiments. In embodiments of this application, the apparatus may be as follows: Figure 4 , Figure 5 , Figure 7 or Figure 8 The first core network element or the second core network element in the method embodiment shown can also be a component (such as a chip, chip system, processor, etc.) configured in the first core network element or the second core network element, or a logic module or software that can implement some or all of the functions of the first core network element or the second core network element.

[0486] The device provided in this application is as follows: Figure 10 As shown, the device 1000 includes a transceiver unit 1010 and a processing unit 1020.

[0487] One possible design is that device 1000 is used to achieve the above. Figure 4 , Figure 5 , Figure 7 or Figure 8 The method embodiment shown illustrates the function of the first core network element. For example, the device 1000 may correspond to... Figure 4 , Figure 5 , Figure 7 or Figure 8 The first core network element in the device 1000 may be, for example, the aforementioned first core network element.

[0488] For example, the processing unit 1020 is used to determine the number of first users based on the characteristic information of the first service of the first terminal user, the number of first users being the number of users simultaneously using the first service; the transceiver unit 1010 is used to send a first message, the first message including the number of first users, and / or the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the number of first users.

[0489] Optionally, the feature information includes at least one of the following: the number of concurrent flows of the first service, the start and end time of each flow in the concurrent flow, the timing relationship between different flows in the concurrent flow, traffic statistics, uplink and downlink messages, or rates.

[0490] Optionally, the transceiver unit 1010 is further configured to receive a second message, which is a poor quality event subscription request message, or a user experience document subscription request message, or a session establishment request message.

[0491] Optionally, the processing unit 1020 is further configured to determine the first number of users based on the first information in the second message and the characteristic information of the first service of the first terminal user, wherein the first information triggers the first core network element to perceive the number of users simultaneously using the first service; or, based on the local configuration of the first core network element taking effect, determine the first number of users based on the characteristic information of the first service of the first terminal user, wherein the local configuration is used to configure the first core network element to perceive the number of users simultaneously using the first service.

[0492] Optionally, the second message is a poor quality event subscription request message, and the first message also includes second information, which is used to characterize the poor quality result and / or QoE result, and the second information is determined based on the first number of users.

[0493] Optionally, the second message is a user experience document subscription request message, and the first message also includes a QoE result, which is determined based on the first number of users.

[0494] Optionally, if the number of users simultaneously using the first service by the first terminal user changes, the transceiver unit 1010 may also be used to send the first message.

[0495] Optionally, the processing unit 1020 is further configured to determine the quality difference result and / or QoE result based on the first number of users.

[0496] Optionally, the second message is a session establishment request message, and the first information includes a policy and charging control matching rule. In the policy and charging control matching rule, the number of at least one candidate users who use the first service at the same time corresponds one-to-one with at least one policy and charging control. The processing unit 1020 is further configured to determine a first policy and charging control based on the number of first users. The first policy and charging control is the policy and charging control corresponding to the number of first users in the policy and charging control matching rule.

[0497] One possible design is that device 1000 is used to achieve the above. Figure 4 , Figure 5 , Figure 7 or Figure 8 The method embodiment shown illustrates the function of the second core network element. For example, the device 1000 may correspond to... Figure 4 , Figure 5 , Figure 7 or Figure 8 The second core network element, among which, Figure 8 For example, the second core network element is Figure 8 The device 1000 may be, for example, the aforementioned second core network element, such as the SMF or PCF in the SMF or PCF.

[0498] For example, the processing unit 1020 is used to determine a second message, the second message including first information, the first information being used to trigger the first core network element to perceive the first user count, the first user count being based on the number of users of the first terminal user simultaneously using the first service; the transceiver unit 1010 is used to send the second message.

[0499] Optionally, the second message is a poor quality event subscription request message, or the second message is a user experience document subscription request message.

[0500] Optionally, the transceiver unit 1010 is further configured to receive a first message, the first message including the first number of users and / or the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the first number of users.

[0501] Optionally, the processing unit 1020 is further configured to determine the guaranteed bandwidth of the first service based on the first number of users.

[0502] Optionally, the second message is a poor quality event subscription request message, and the first message also includes second information, which is used to characterize the poor quality result and / or QoE result, and the second information is determined based on the first number of users.

[0503] Optionally, the second message is a user experience document subscription request message, and the first message also includes a QoE result, which is determined based on the first number of users.

[0504] Optionally, the processing unit 1020 is further configured to determine at least one of the following based on the first message: an experience map, user perception analysis results, or a visual interface for guarantee effects.

[0505] Optionally, the first message may also be used to indicate a change in the number of users simultaneously using the first service for the first account.

[0506] Optionally, the processing unit 1020 is also configured to determine the ABR based on the first number of users.

[0507] Optionally, the transceiver unit 1010 is further configured to receive a third message from a policy control function network element, the third message including the first information.

[0508] Optionally, the second core network element is a policy control network element.

[0509] Optionally, the first information includes policy and charging control matching rules, wherein the policy and charging control matching rules correspond one-to-one with at least one policy and charging control based on the number of at least one candidate user who simultaneously uses the first service.

[0510] For a more detailed description of the transceiver unit 1010 and the processing unit 1020, please refer to [link / reference needed]. Figure 4 , Figure 5 , Figure 7 or Figure 8 The relevant descriptions in any of the embodiments shown are directly obtained and will not be repeated here.

[0511] In one possible design, when the device 1000 is a network device (i.e., the aforementioned first core network element or second core network element) or a communication module within a network device, the function of the processing unit 1020 can be implemented by one or more processors. Specifically, the processor may include a modem chip, or a system-on-a-chip (SoC) chip or a SIP chip containing a modem core. The function of the transceiver unit 1010 can be implemented by transceiver circuitry.

[0512] In one possible design, when the device 1000 is a circuit or chip responsible for communication functions in a network device, such as a modem chip or a system-on-a-chip (SoC) or SIP chip containing a modem core, the function of the processing unit 1020 can be implemented by a circuit system in the aforementioned chip that includes one or more processors or processor cores. The function of the transceiver unit 1010 can be implemented by interface circuitry or data transceiver circuitry on the aforementioned chip.

[0513] It should also be understood that the transceiver unit in the communication device 1000 can also be called a communication unit. This transceiver unit 1010 may include a transmitting unit but not a receiving unit. Alternatively, the transceiver unit 1010 may include a receiving unit but not a transmitting unit. Specifically, it depends on whether the above-described scheme performed by the device 1000 includes both transmitting and receiving actions. The receiving unit can be used to perform the receiving action in the above-described scheme, and the transmitting unit can be used to perform the transmitting action in the above-described scheme.

[0514] It is understood that the division of units in the above-described device is merely a logical functional division. Each function can correspond to a functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into a single physical entity, or they can be distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0515] Figure 11 This is another schematic block diagram of the device provided in the embodiments of this application. For example... Figure 11 As shown, device 1100 includes one or more processors 1110. The processor 1110 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the device (e.g., a vehicle or a chip), execute software programs, and process data from the software programs.

[0516] Optionally, in one design, processor 1110 may include a computer program (also referred to as code or instructions) that can be executed on processor 1110, causing device 1100 to perform the methods performed by the first core network element or the second core network element in the above method embodiments. In yet another possible design, device 1100 includes circuitry (…). Figure 11 (Not shown), this circuit is used to implement the function of the first core network element or the second core network element in the above method embodiment.

[0517] For example, processor 1110 can be used to execute a computer program in memory to achieve Figure 4 , Figure 5 , Figure 7 or Figure 8 The steps performed by the first core network element or the second core network element in the illustrated embodiment.

[0518] Optionally, the device 1100 may include one or more memories 1120 storing computer programs (sometimes referred to as code or instructions) that can be run on the processor 1110, causing the device 1100 to perform the methods performed by the first core network element or the second core network element in the above embodiments.

[0519] Optionally, the processor 1110 and / or memory 1120 may also store data. The processor and memory may be configured separately or integrated together.

[0520] Optionally, the device 1100 may further include a communication interface 1130. The processor 1110, sometimes referred to as a processing unit, controls the device (e.g., a first core network element or a second core network element). The communication interface 1130, sometimes referred to as a transceiver unit, transceiver, transceiver circuit, or transceiver, is used to implement the device's transceiver functions; for example, the communication interface 1130 can be used to receive a first message.

[0521] Optionally, the device 1100 also includes a communication interface 1130. The processor 1110 and the communication interface 1130 are coupled to each other. It is understood that the communication interface 1130 can be a transceiver or an input / output interface.

[0522] When device 1100 is used to achieve Figure 4 , Figure 5 , Figure 7 or Figure 8 In the method shown, processor 1110 can be used to execute the functions of processing unit 1020, and communication interface 1130 can be used to execute the functions of transceiver unit 1010. Whether communication interface 1130 is used for sending or receiving depends on whether the device 1100 is used to perform a sending or receiving operation in the execution scheme.

[0523] When the aforementioned device 1100 is a chip applied to a first core network element, the chip implements the functions of the first core network element in the above method embodiment. The chip of the first core network element receives signals from other modules (such as radio frequency modules or antennas) in the first core network element, and these signals may be sent from the second core network element to the first core network element; or, the chip of the first core network element sends signals to other modules (such as radio frequency modules or antennas) in the first core network element, and these signals may be sent from the first core network element to the second core network element.

[0524] When the aforementioned device 1100 is a chip applied to a second core network element, the chip implements the functions of the second core network element in the above method embodiment. The chip of the second core network element receives signals from other modules within the second core network element; these signals may be sent from the first core network element to the second core network element. Alternatively, the chip of the second core network element sends signals to other modules within the second core network element; these signals may be sent from the second core network element to the first core network element.

[0525] It is understood that when the device 1100 is a first core network element or a second core network element, the communication interface 1130 can be a transceiver, specifically including a transmitter and a receiver, with the transmitter used to send signals and the receiver used to receive signals. When the device 1100 is a chip applied to a first core network element or a second core network element, the communication interface 1130 can be an input / output circuit, wherein the input circuit can be used for receiving and the output interface can be used for sending.

[0526] Optionally, the device 1100 also includes a power supply circuit for supplying power to the device 1100.

[0527] It should be noted that the above method embodiments can be applied to a processor, or implemented by a processor. A processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by software instructions.

[0528] The processors mentioned above can be general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof. General-purpose processors can be microprocessors or any conventional processor, etc.

[0529] The steps of the method disclosed in the embodiments of this application can be directly manifested as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can reside in mature storage media in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0530] The memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0531] This application also provides a chip system including at least one processor for supporting the implementation of the functions of the first core network element or the second core network element involved in any of the above method embodiments, such as receiving, transmitting, or processing the information involved in the above methods.

[0532] In one possible design, the chip system also includes a memory for storing computer program instructions and data, which may be located inside or outside the processor.

[0533] The chip system can consist of chips or include chips and other discrete components.

[0534] This application also provides a computer program product comprising: a computer program (also referred to as code or instructions), which, when executed, Figure 4 , Figure 5 , Figure 7 or Figure 8In the illustrated embodiment, the method executed by the first core network element or the method executed by the second core network element is executed.

[0535] This application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is run, Figure 4 , Figure 5 , Figure 7 or Figure 8 In the illustrated embodiment, the method executed by the first core network element or the method executed by the second core network element is executed.

[0536] This application also provides a communication system, which includes the aforementioned first core network element and second core network element.

[0537] The methods provided in the above embodiments can be implemented, in whole or in part, by software, hardware, firmware, or any combination thereof. When implemented in software, they can be implemented, in whole or in part, in the form of a computer program product. This computer program product may include one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic disk), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

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

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

[0540] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0541] The unit described as a separate component may or may not be physically separate. The component shown as a unit may or may not be a physical unit; that is, it may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

[0543] If this function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, or part of it, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory, random access memory, magnetic disks, or optical disks.

Claims

1. A communication method, characterized in that, Applied to the first core network element, the method includes: Based on the characteristic information of the first service of the first terminal user, the number of first users is determined, where the number of first users is the number of users who use the first service at the same time. Send a first message, the first message including the first number of users, and / or the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the first number of users.

2. The method according to claim 1, characterized in that, The feature information includes at least one of the following: the number of concurrent flows of the first service, the start and end time of each flow in the concurrent flow, the timing relationship between different flows in the concurrent flow, traffic statistics, uplink and downlink messages, or rates.

3. The method according to claim 1 or 2, characterized in that, The method further includes: Receive a second message, which is either a poor quality event subscription request message, a user experience document subscription request message, or a session establishment request message.

4. The method according to claim 3, characterized in that, Determining the number of first users based on the feature information of the first service of the first terminal user includes: Based on the first information in the second message, and based on the characteristic information of the first service of the first terminal user, the first number of users is determined, wherein the first information triggers the first core network element to perceive the number of users simultaneously using the first service; or... Based on the local configuration of the first core network element taking effect, and based on the characteristic information of the first service of the first terminal user, the number of first users is determined. The local configuration is used to configure the first core network element to sense the number of users simultaneously using the first service.

5. The method according to claim 3, characterized in that, The second message is a poor quality event subscription request message. The first message also includes second information, which is used to characterize the poor quality result and / or the business experience quality (QoE) result. The second information is determined based on the first number of users.

6. The method according to claim 3, characterized in that, The second message is a user experience document subscription request message, and the first message also includes the business experience quality (QoE) result, which is determined based on the first number of users.

7. The method according to claim 5 or 6, characterized in that, Sending the first message includes: The first message is sent when the number of users simultaneously using the first service by the first terminal user changes.

8. The method according to claim 5 or 6, characterized in that, The method further includes: determining the quality difference result and / or QoE result based on the first number of users.

9. The method according to claim 4, characterized in that, The second message is a session establishment request message. The first information includes policy and charging control matching rules, wherein the number of at least one candidate user using the first service simultaneously corresponds one-to-one with at least one policy and charging control in the policy and charging control matching rules. The method further includes: Based on the first number of users, a first policy and billing control are determined. The first policy and billing control is the policy and billing control corresponding to the first number of users in the policy and billing control matching rules.

10. A communication method, characterized in that, Applied to the second core network element, the method includes: A second message is determined, the second message includes first information, the first information is used to trigger the first core network element to perceive the first number of users, the first number of users is based on the number of users of the first terminal user who are simultaneously using the first service; Send the second message.

11. The method according to claim 10, characterized in that, The second message is a poor quality event subscription request message, or the second message is a user experience document subscription request message.

12. The method according to claim 10 or 11, characterized in that, The method further includes: Receive a first message, the first message including the first number of users, and / or the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the first number of users.

13. The method according to claim 12, characterized in that, The second message is a poor quality event subscription request message. The first message also includes second information, which is used to characterize the poor quality result and / or the business experience quality (QoE) result. The second information is determined based on the first number of users.

14. The method according to claim 12, characterized in that, The second message is a user experience document subscription request message, and the first message also includes a business experience quality (QoE) result, which is determined based on the first number of users.

15. The method according to claim 13 or 14, characterized in that, The first message is a user experience awareness information notification message, and the method further includes: Based on the first message, at least one of the following is determined: experience map, user perception analysis results, or visual interface for guarantee effect.

16. The method according to claim 15, characterized in that, The first message is also used to indicate that the number of users of the first terminal user who are simultaneously using the first service has changed.

17. The method according to claim 16, characterized in that, The first message includes the first number of users, and the method further includes: Based on the first number of users, the guaranteed bandwidth for the first service is determined.

18. The method according to claim 16 or 17, characterized in that, The method further includes: Based on the first number of users, determine the adaptive bitrate (ABR).

19. The method according to claim 10, characterized in that, The second core network element is a session management function network element, and the method further includes: Receive a third message from the policy control function network element, the third message including the first information.

20. The method according to claim 10, characterized in that, The second core network element is the policy control network element.

21. The method according to claim 19 or 20, characterized in that, The first information includes policy and charging control matching rules, wherein the policy and charging control matching rules are based on the number of at least one candidate users who simultaneously use the first service and at least one policy and charging control.

22. A communication device, characterized in that, It includes modules for implementing the method as described in any one of claims 1 to 9, or includes modules for implementing the method as described in any one of claims 10 to 21.

23. A communication device, characterized in that, The device includes one or more processors, which are configured to execute computer programs or instructions in memory, causing the communication device to perform the method as described in any one of claims 1 to 9, or to perform the method as described in any one of claims 10 to 21.

24. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it causes the method as described in any one of claims 1 to 9 to be performed, or causes the method as described in any one of claims 10 to 21 to be performed.

25. A computer program product, characterized in that, Includes a computer program that, when run, causes the method as described in any one of claims 1 to 9 to be performed, or causes the method as described in any one of claims 10 to 21 to be performed.

Images