Communication method, device and system

Abstract

The invention provides a communication method, device and system. In the method, a first core network element can report a first user number to a second core network element through first information, the first user number is the number of users who use a first service at the same time through a first terminal user, and the first user number can be determined based on feature information of the first service, and / or the first user number can be determined based on the feature information of the first service. The first core network element can determine the guaranteed bandwidth of the first service based on the first user number, and then can report the guaranteed bandwidth of the first service to the second core network element through the first information. Therefore, the experience guarantee can be ensured when a plurality of users use the first service at the same time.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a communication method, device, and system. Background Art

[0002] With the continuous development of tethering technology, multiple terminals can be mounted on a single customer-premises equipment (CPE) or mobile phone. These multiple terminals can directly provide network access, enabling multi-user concurrency.

[0003] Currently, the user plane function (UPF) can perceive individual application (APP) services, thereby obtaining service quality of experience (QoE) and / or quality degradation results for different APP services. When a quality degradation event occurs, the network data analytics function (NWDAF) can achieve the desired service experience by establishing a dedicated bearer with a guaranteed bit rate (GBR) or a QoS flow identifier (QFI) based on the bandwidth required for the service experience.

[0004] However, when multiple users are concurrently using the same business scenario, NWDAF is not sufficient to support the experience assurance needs of multiple users concurrently based on the single-user APP business experience assurance needs. Summary of the Invention

[0005] The present application provides a communication method, device and system to improve the service experience guarantee of multiple users concurrently.

[0006] In a first aspect, a communication method is provided. The communication method can be applied to a communication device. The communication device can be, for example, a first core network element, or a component configured in the first core network element (such as a chip, a chip system, a processor, etc.), or a logic module or software capable of implementing all or part of the functions of the first core network element. This application is not limited to this.

[0007] Exemplarily, the method includes: determining a first number of users based on characteristic information of a first service of a first terminal user, where the first number of users is the number of users who simultaneously use the first service; sending a first message, where the first message includes the first number of users and / or the guaranteed bandwidth of the first service, where the guaranteed bandwidth is determined based on the first number of users.

[0008] Based on the above solution, 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 (referred to as the number of first users) who are simultaneously using the first service through the first terminal user based on the characteristic information of the first service, and then report the number of first users to the second core network element. Alternatively, the first core network element can determine the guaranteed bandwidth for the first service based on the number of first users, and then report the guaranteed bandwidth for the first service to the second core network element. In this way, the user experience can be improved when multiple users simultaneously use the first service.

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

[0010] In combination with the first aspect, in some possible implementations of the first aspect, the characteristic information includes 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 information, uplink and downlink messages, or at least one of the rates.

[0011] For example, the first core network element can calculate, based on characteristic information of users using the first service within a period, various mathematical methods to obtain derived features of each characteristic information item. Furthermore, based on the derived features of each characteristic information item, an artificial intelligence (AI) model or algorithm 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 can be understood that the characteristic information includes 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 information, uplink and downlink messages, or at least one of the rates are only examples. For example, other indicators of the first service may also be included, and this application does not limit this.

[0013] In combination with the first aspect, in some possible implementations of the first aspect, the method also includes: receiving a second message, the second message being a quality difference event subscription request message, or the second message being a user experience document subscription request message, or the second message being 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 switch or parameter of the perception function of the number of users who simultaneously use the first service through the first terminal user.

[0015] That is, the first core network element adds a function of sensing the number of users who simultaneously use the first service through the first terminal user, and can add it to the existing solution framework through interface definition.

[0016] For different application scenarios, the second message may be different request messages.

[0017] For example, for a key service assurance solution for VIP users, the second message may be a quality-poor event subscription request message, and based on the second message, accurate quality-poor perception and assurance processes may be implemented in a multi-user concurrent scenario.

[0018] For another example, in the scenario of experience map, user perception analysis results or guarantee effect visualization, the second message can be a user experience document subscription request message. Based on the second message, the indicator of the number of concurrent users can be presented in the experience map, user perception analysis results or guarantee effect visual interface.

[0019] For another example, in the PCC content charging and control solution, the second message may be a session establishment request message, and based on the second message, the business process of perception of different numbers of concurrent users and differentiated policies and charging control can be implemented.

[0020] In this way, in different application scenarios, different requirements can be achieved based on the second message.

[0021] In combination with the first aspect, in some possible implementations of the first aspect, the determining of 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 network element to perceive the number of users who simultaneously use the first service; or, taking effect according to the local configuration of the first core network network element, determining the number of first users based on the characteristic information of the first service of the first terminal user, and the local configuration is used to configure the first core network network element to perceive the number of users who simultaneously use the first service.

[0022] One possible scenario is that the first core network element can enable the first core network element to increase its perception of the number of users who simultaneously use the first service based on the first information in the second information, so that the number of first users who simultaneously use the first service can be determined through an AI algorithm or model based on the characteristic information of the first terminal user using the first service within a period.

[0023] One possible scenario is that the first core network element can configure local configuration through commands, and based on the effectiveness of the local configuration, the first core network element can be enabled to increase its perception of the number of users who simultaneously use the first service, so that the number of first users who simultaneously use the first service can be determined through an AI algorithm or model based on the characteristic information of the first terminal user using the first service within a period.

[0024] In this way, the first core network element can be enabled to increase its ability to perceive the number of users who are simultaneously using the first service, which helps the operator to accurately perceive the concurrent status of multiple users of the first service in the network based on this function, thereby achieving service protection for different users (for example, key services for VIP users) or accurate perception, protection and management under differentiated billing and control strategies.

[0025] In combination with the first aspect, in some possible implementations of the first aspect, the second message is a quality difference event subscription request message, and the first message also includes second information, which is used to characterize the quality difference result and / or QoE result, and the second information is determined based on the first number of users.

[0026] The first core network element can determine the first number of users through perception and adjust the algorithm or model used to obtain the quality difference result and / or QoE result based on the first number of users. For example, the first number of users can be used as an output parameter to optimize the quality difference evaluation and / or QoE evaluation algorithm or model, so that the quality difference evaluation and / or QoE evaluation algorithm or model can be adapted to obtain the quality difference result and / or QoE result in a multi-user concurrent scenario. Furthermore, the first core network element can obtain a more accurate quality difference result and / or QoE result based on the adjusted algorithm or model.

[0027] This will help operators accurately perceive the concurrent status of multiple users of the primary service in the network based on this function, and achieve accurate QoE evaluation and quality difference perception in key service guarantees for VIP users, and provide effective bandwidth guarantees required for the experience.

[0028] In combination 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 service experience quality QoE result, and the service experience quality QoE result is determined based on the first number of users.

[0029] The first core network element can adjust an algorithm or model used to obtain a QoE result based on the first number of users determined through sensing. For example, the algorithm or model used to obtain a QoE evaluation result can be optimized by using the first number of users as an output parameter, so that the QoE evaluation algorithm or model can adapt to obtaining a QoE result in a multi-user concurrent scenario. Furthermore, the first core network element can obtain a more accurate QoE result based on the adjusted algorithm or model.

[0030] This will help operators accurately perceive the concurrent status of multiple users of the primary service in the network based on this function, achieve accurate QoE evaluation in key service guarantees, and provide effective bandwidth guarantees required for the experience.

[0031] In combination 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 of the first terminal user who simultaneously use the first service changes.

[0032] The first core network element may continuously monitor the number of the first users, and when the number of the first users changes, the first core network element may be triggered to report the first message to the second core network element.

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

[0034] In this way, the number of users who simultaneously use the first service through the first terminal user can be dynamically reported to the second core network element, so that the second core network element can dynamically adjust the guaranteed bandwidth of the first service, thereby providing the effective bandwidth guarantee required by users experiencing the first service.

[0035] In combination with the first aspect, in some possible implementations of the first aspect, the method further includes: determining the quality difference result and / or the 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 may 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 results and / or QoE results can be obtained.

[0038] In combination with the first aspect, in some possible implementations of the first aspect, the second message is a session establishment request message, the first information includes a policy and charging control (PCC) matching rule, and the policy and charging control matching rule has a one-to-one correspondence between at least one candidate user number who simultaneously uses the first service and at least one policy and charging control. The method also includes: determining a first policy and charging control based on the first number of users, and 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 rule.

[0039] The policy and charging control matching rules carried in the second message include a matching rule based on the number of first users. For example, different policy and charging controls may correspond to different numbers of first users. The first core network element may implement differentiated management and control policies and charging policies for different numbers of first users based on the policy and charging control matching rules carried in the second message.

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

[0041] In a second aspect, a communication method is provided, which can be applied to a communication device. The communication device can be, for example, a second core network element, or a component configured in the second core network element (such as a chip, a chip system, a processor, etc.), or a logic module or software capable of implementing all or part of the functions of the second core network element. This application is not limited to this.

[0042] Exemplarily, 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 number of users, the first number of users being based on the number of first terminal users who simultaneously use the first service; and sending the second message.

[0043] Based on the above solution, the second core network element, through the first information carried in the second message sent, enables the first core network element to trigger, based on the first information, the first core network element to perceive the number of users (denoted as the first number of users) concurrently using the first service based on the first terminal user. This enables the first core network element to increase its ability to perceive the number of users concurrently using the first service, thereby improving the user experience when multiple users concurrently use the first service based on this perception capability.

[0044] In combination 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 receipt subscription request message.

[0045] In combination 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 combination with the second aspect, in some possible implementations of the second aspect, the first message includes the number of first users, and the method further includes: determining a guaranteed bandwidth for the first service based on the number of first users.

[0047] The first message reported by the first core network element to the second core network element includes the number of first 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 number of first users and the guaranteed bandwidth when a single user uses the first service, where n represents the number of first users.

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

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

[0050] In combination 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 service experience quality QoE result, and the service experience quality QoE result is determined based on the first number of users.

[0051] In combination 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 also includes: based on the first message, determining at least one of the following: an experience map, a user perception analysis result, or a guarantee effect visual interface.

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

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

[0054] In combination with the second aspect, in some possible implementations of the second aspect, the first message is further used to indicate a change in the number of users of the first account who simultaneously use the first service.

[0055] That is, the first core network element may continuously monitor the number of first users, and when the number of first users changes, the first core network element may be triggered to report the first message to the second core network element.

[0056] Optionally, when a poor quality event occurs, the first core network element may 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 who simultaneously use the first service through the first terminal user reported by the first core network element, thereby providing the effective bandwidth guarantee required by users experiencing the first service.

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

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

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

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

[0062] That is, the third message may include the first information for triggering the first core network element to perceive the first number of users, where the first number of users is based on the number of first terminal users who simultaneously use the first service.

[0063] The third message can be interacted through the N7 interface, that is, the N7 interface can extend the definition of the switch or parameter of the perception function of the number of users who simultaneously use the first service through the first terminal user.

[0064] That is, the PCF may send the third message to the SMF via the N7 interface. Correspondingly, the SMF may receive the third message from the PCF via the N7 interface.

[0065] Similarly, when SMF sends a second message to the first core network element, the second message can be interacted through the N4 interface, that is, the N4 interface can expand the definition of the switch or parameters of the perception function of the number of users who simultaneously use the first service through the first terminal user.

[0066] That is, the SMF may send the second message to the first core network element via the N4 interface. Correspondingly, the first core network element may receive the second message from the SMF via the N4 interface.

[0067] In other words, the first core network element can add a function of sensing the number of users who simultaneously use the first service through the first terminal user to the existing solution framework through interface definition.

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

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

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

[0071] It can be understood that the second message sent by PCF to SMF and the third message that the aforementioned PCF can send to SMF through the N7 interface are the same message. Different names are used only to distinguish which core network element the second core network element is, and should not constitute any limitation to the embodiments of the present 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 combination with the second aspect, in some possible implementations of the second aspect, the first information includes a policy and billing control matching rule, in which at least one number of candidate users based on the first terminal user simultaneously using the first service corresponds one-to-one with at least one policy and billing control.

[0074] The first information included in the second message and the third message includes policy and charging control matching rules. Different numbers of users may correspond to different policies and charging controls.

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

[0076] For the relevant content of the second aspect, please refer to the detailed description in the first aspect and will not be repeated here.

[0077] In a third aspect, the present application provides a communication device, comprising modules or units for implementing the method in the first aspect and any possible implementation of the first aspect. Each module or unit can implement the corresponding function by executing a computer program.

[0078] In a fourth aspect, the present application provides a communication device, comprising a processor, wherein the processor is configured to execute the communication method described in the first aspect and any possible implementation manner of the first aspect.

[0079] The apparatus may further include a memory for storing instructions and data. The memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the methods described in the above aspects may be implemented. The apparatus may further include a communication interface for communicating between the apparatus and other devices. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

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

[0081] In a fifth aspect, the present application provides a chip system comprising at least one processor for supporting the implementation of the functions involved in the above-mentioned first aspect and any possible implementation of the first aspect, for example, receiving or processing the information involved in the above-mentioned method.

[0082] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0083] The chip system can be composed of chips, or can include chips and other discrete devices.

[0084] In a sixth aspect, the present application provides a communication device, comprising modules or units for implementing the method in the second aspect and any possible implementation of the second aspect. Each module or unit can implement the corresponding function by executing a computer program.

[0085] In a seventh aspect, the present application provides a communication device, comprising a processor, wherein the processor is configured to execute the communication method described in the second aspect and any possible implementation manner of the second aspect.

[0086] The apparatus may further include a memory for storing instructions and data. The memory is coupled to the processor, and when the processor executes the instructions stored in the memory, the methods described in the above aspects may be implemented. The apparatus may further include a communication interface for communicating between the apparatus and other devices. Exemplarily, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.

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

[0088] In an eighth aspect, the present application provides a chip system comprising at least one processor for supporting the implementation of the functions involved in the above-mentioned second aspect and any possible implementation of the second aspect, for example, receiving or processing the information involved in the above-mentioned method.

[0089] In one possible design, the chip system further includes a memory, which is used to store program instructions and data, and the memory is located inside or outside the processor.

[0090] The chip system can be composed of chips, or can include chips and other discrete devices.

[0091] In a ninth aspect, the present application provides a computer-readable storage medium comprising a computer program, which, when executed on a computer, enables the computer to implement the method in the first or second aspect and any possible implementation of the first or second aspect.

[0092] In the tenth aspect, the present application provides a computer program product, which includes: a computer program (also referred to as code, or instructions), which, when executed, enables a computer to execute the method in the first or second aspect and any possible implementation of the first or second aspect.

[0093] In the eleventh aspect, an embodiment of the present application provides 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 methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[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 hotspot technology provided by the embodiment of the present 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 an embodiment of the present application;

[0098] Figure 4 is a schematic flow chart of a communication method provided in an embodiment of the present application;

[0099] Figure 5 is another schematic flow chart of the communication method provided in an embodiment of the present application;

[0100] Figure 6 This is a diagram of the QoE and / or quality difference evaluation algorithm architecture provided by an embodiment of the present application;

[0101] Figure 7 is another schematic flow chart of the communication method provided in an embodiment of the present application;

[0102] Figure 8 is another schematic flow chart of the communication method provided in an embodiment of the present application;

[0103] Figure 9 This is another schematic diagram of a network system architecture provided by an embodiment of the present application;

[0104] Figure 10 is a schematic diagram of a communication device provided in an embodiment of the present application;

[0105] Figure 11 This is another schematic diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0106] The technical solution provided in this application will be described below in conjunction with the accompanying drawings.

[0107] To facilitate understanding of the embodiments of the present application, the following points are first explained:

[0108] First, in this application, indications include explicit indications (also called direct indications) and implicit indications (also called indirect indications). Explicit indications of information A include information A; implicit indications of information A indicate information A through the correspondence between information A and information B, as well as through direct indication of information B. The correspondence between information A and information B can be predefined, pre-stored, pre-burned, or pre-configured; alternatively, information A can be indicated through information B and preset rules.

[0109] Second, in this application, information C is used to determine information D, which includes both information D being determined solely based on information C and information D being determined based on information C and other information. Furthermore, information C can also be used to determine information D indirectly, for example, when 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" means two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship, but it does not exclude the situation where it indicates that the previous and next associated objects are in an "and" relationship. The specific meaning can be understood in conjunction with the context. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a, b, and c. Where a, b, and c can be single or plural.

[0111] Fourth, in this application, prefixes such as "first" and "second" are used solely to distinguish between different items belonging to the same category and do not constrain the order, size, or quantity of items. For example, "first message" and "second message" are simply different messages; there is no temporal, size, or priority relationship between them.

[0112] Fifth, "sending" and "receiving" in this application indicate the direction of signal transmission. For example, "sending information to the first core network network element" can be understood as the destination end of the information is the first core network network element, which can include direct sending through the air interface, and also include indirect sending through the air interface by other units or modules. "Receiving information from the second core network network element" can be understood as the source end of the information is the second core network element, which can include direct receiving from the second core network element through the air interface, and also include indirect receiving from the second core network element through the air interface from other units or modules. "Sending" can also be understood as the "output" of the chip interface, and "receiving" can also be understood as the "input" of the chip interface.

[0113] In other words, sending and receiving can be carried out between devices, for example, between the first core network element and the second core network element; it can also be carried out within the device, for example, sending or receiving between components, modules, chips, software modules or hardware modules within the device through 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) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, sidelink (SL) communication system, universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) mobile communication system or new radio access technology (NR). Among them, 5G mobile communication system 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 sixth generation (6G) mobile communication system. This application does not limit this.

[0115] Figure 1 This is a schematic diagram of a network system architecture applicable to the method provided in the embodiment of the present 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 may also be called user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.

[0117] A terminal device is a device with wireless transceiver capabilities. The terminal device can communicate with one or more core network (CN) devices (or core devices) via an access network device (or access device) in a wireless access network. The terminal device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water (such as ships); or in the air (such as on airplanes, balloons, and satellites). In embodiments of the present application, the terminal device can be a terminal device in an Internet of Things (IoT) system. For example, the terminal device can be an ambient internet of things (A-IoT, or AIoT) device. IoT is an important component of future information technology development. Its main technical feature is connecting objects to the network through communication technology, thereby realizing an intelligent network that interconnects humans and machines, and objects and things. Connections can be made through broadband or narrowband (NB) technology. IoT technology, for example, can achieve massive connections, deep coverage, and power-saving terminals through narrowband technology.

[0118] In the embodiments of the present application, the device for realizing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to realize the function, such as a chip system, which can be installed in the terminal device or used in combination with the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or it can include a chip and other discrete devices. In the embodiments of the present application, only the terminal device is used as an example for description, and the embodiments of the present application are not limited to the solutions of the embodiments of the present application.

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

[0120] In the embodiments of the present application, a radio access network device can be any device with wireless transceiver capabilities. A radio access network device can provide wireless communication services and connect terminal devices to a wireless network. A radio access network can also be referred to as an access network device or a network device. A radio access network device can also be referred to as 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 sixth-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 base 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 terminals in achieving wireless access, with different RAN nodes implementing portions of the base station's functionality. For example, a RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be separate or included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH).

[0123] In different systems, the CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meanings. For example, in an open access network (open RAN, O-RAN, or ORAN) system, the CU may also be referred to as an open CU (O-CU), the DU may also be referred to as an O-DU, the CU-CP may also be referred to as an O-CU-CP, the CU-UP may also be referred to as an O-CU-UP, and the RU may also be referred to as an O-RU. For ease of description, this application uses the CU, CU-CP, CU-UP, DU, and RU as examples. Any of the CU (or CU-CP, CU-UP), DU, and RU in this application may be implemented as 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 module (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 single network slice selection assistance information (S-NSSAI) for the UE.

[0126] NEF can be used to open the 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, 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 mainly performs policy control on quality of service (QoS) and charging.

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

[0130] The AF primarily communicates application-side requests to the network and can be considered an application server or an application server proxy. It can provide certain application-layer services to terminal devices. When providing services to terminal devices, the AF has requirements for billing and QoS policies, which it must notify the network of. Furthermore, the AF requires core network devices to provide feedback on application-related information.

[0131] EASDF mainly 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 mainly provides 3GPP and non-3GPP unified access authentication services.

[0134] The AMF mainly performs functions such as mobility management and access authentication / authorization. In addition, the AMF network element is also responsible for transmitting user policies between terminal devices and PCF network elements.

[0135] SMF mainly performs session management, allocation and management of Internet Protocol (IP) addresses of user devices, and UPF selection.

[0136] SCP is a control plane message routing intermediary that enables indirect communication between NFs.

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

[0138] The UPF is primarily used for packet routing and forwarding, policy and QoS processing, and usage reporting. As a DN-supported interface, the UPF performs user plane data forwarding, session- and flow-level billing and statistics, and bandwidth limiting. User data can be sent to data networks (such as the Internet) through this network element.

[0139] DN mainly provides business services to users.

[0140] Network elements communicate with each other through interfaces. For example, the signaling plane interface between the terminal device and the AMF is the N1 interface. Since the terminal device cannot interact directly with the core network equipment, it must transparently transmit non-access stratum (NAS) information through the access stratum (AS). The signaling plane interface through which the AMF requests the access network (AN) to allocate resources for protocol data unit (PDU) sessions is the N2 interface. The signaling plane interface between the UPF and SMF is the N4 interface, and so on. These interfaces are not listed here, 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 does not constitute any limitation on this application. Furthermore, the various network elements shown in the figure can be understood as network elements used to implement different functions in the core network, for example, they can be combined into network slices as needed. These core network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of these network elements.

[0142] It can be understood that the network elements used in future communication systems can be the above-mentioned network elements, or can be network elements with other names that have the same or similar functions. This application does not limit this.

[0143] In the embodiments of the present application, access network devices and core network elements may be collectively referred to as network devices. The device used to implement the functions of the network device may be a network device; it may also be a device capable of supporting the network device in implementing the functions, such as a chip system, a hardware circuit, a software module, or a hardware circuit and a software module. The device may be installed in the network device or used in conjunction with the network device. The embodiments of the present application are described using the network device as an example, and do not limit the embodiments of the present application.

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

[0145] Figure 2 Figure 2 is a schematic diagram of the hotspot technology provided in an embodiment of the present application. The hotspot feature is derived from the introduction of shared hotspot devices such as wireless fidelity (Wi-Fi) and mobile Wi-Fi (MiFi). Specifically, a mobile network card or CPE can directly provide Wi-Fi hotspots for different terminal devices, such as laptops, smartphones, and tablets. Users can enable the hotspot function on different terminal devices, and the terminal devices providing the hotspot function are referred to as hotspot users.

[0146] in, Figure 2 (a) shows that a smartphone provides Wi-Fi hotspots to different terminal devices through Wi-Fi connection; Figure 2 (b) in the figure shows that a smartphone provides a hotspot to different terminal devices through a physical connection via a universal serial bus (USB).

[0147] Figure 2 (c) in the figure shows that a smartphone provides a hotspot to different terminal devices via Bluetooth connection.

[0148] Figure 3 This is a schematic diagram of the NWDAF data subscription collection, data analysis, and analysis result subscription and notification mechanism provided by the embodiment of this application. Figure 3 The solid line in the figure represents the data analysis and assurance process, the dotted line a represents the subscription process, and the dotted line b represents data generation.

[0149] from Figure 3 As can be seen, PCF includes the following modules: intelligent decision-making, VIP package subscription, NWDAF addressing, and PCF session management. Intelligent decision-making includes dynamic protection rules, protection policy generation, and QoS decision-making.

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

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

[0152] NWDAF consists of the following modules: the analytics logical function (AnLF) and the data platform. The AnLF includes analysis and subscription management, UPF addressing, guarantee policy and QoS generation, guarantee effect evaluation, visualization, and SMS notifications. The data platform includes data collection and the issuance of quality-critical subscriptions.

[0153] For details about NWDAF data subscription collection, data analysis, and analysis result subscription and notification mechanisms, please refer to the relevant descriptions 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 have launched VIP (very important person, VIP) key service assurance packages and configured services related to these packages in the business and operations support system (BOSS) and PCF. The user data gateway (UDG) deploys SA service identification capabilities to identify guaranteed app flows. Operations, administration, and maintenance (OAM) can regularly report wireless metrics to the NWDAF. The specific process is as follows:

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

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

[0157] 3. Based on the analytics ID carried in the subscription message sent 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] Exemplarily, the NWDAF sends a subscription data collection request message to the SMF (e.g., using the Nsmf_EventExposure_Subscribe message). The SMF further sends a subscription data collection request message to the UPF. The subscription data collection request message carries key information such as the rules and the af APP ID. Based on the rules and af APP ID, the UPF can determine which app flows of which users need to perform quality detection.

[0159] The NWDAF can address the UPF that can provide VIP service guarantee under the coverage area based on the tracking area identity (TAI) information, and subscribe to the quality difference information of the VIP package group (group) from the UPF.

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

[0161] For example, the NWDAF may send a poor quality event subscription request message to the UPF. The poor quality event subscription request message may be a poor quality event subscription request message for VIP user APPs.

[0162] Accordingly, UPF can report the VIP user APPs poor quality event notification message to NWDAF.

[0163] For another example, the NWDAF may send a user experience document subscription request message to the UPF. The user experience document subscription request message may be, for example, a common user experience document subscription request message.

[0164] Accordingly, UPF may report user-level service experience perception information notification message to NWDAF.

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

[0166] 5. After receiving the poor quality event, the NWDAF can extract the af APP ID and obtain information such as the guaranteed bandwidth and latency required by the APP. It can also extract key information such as the flow quintuple to make a QoS recommendation to the PCF. For example, the NWDAF can send the PCF the results of the poor quality data analysis (for example, via the Nnwdaf_EventSubscription_Notify message).

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

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

[0169] The SMF triggers the UPF and RAN to successfully establish a dedicated bearer. Service data is transmitted on the GBR dedicated bearer or QFI, with transmission bandwidth and processing latency prioritized, improving the service experience.

[0170] Based on the current solution, the UPF can perceive different services and obtain QoE results. When a subscriber's service quality deteriorates, i.e., a quality degradation event occurs, the NWDAF can improve the experience of key services by establishing a dedicated bearer with GBR guarantee or QFI based on the bandwidth required to ensure the service experience.

[0171] However, the current solution is based on the service experience guarantee needs of a single user for a certain service, which is not sufficient to support the service experience guarantee needs in multi-user concurrent scenarios.

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

[0173] For example, in scenarios where key services require poor quality, NWDAF can recommend guaranteed bandwidth based on the bandwidth requirements of a single user's service experience. However, in scenarios where multiple users are concurrently using the service, the guaranteed bandwidth recommended by NWDAF may not be sufficient to support the experience requirements of multiple users concurrently.

[0174] In view of this, the present application provides a communication method, in which a first core network element can determine the number of users (recorded as the number of first users) who simultaneously use the first service through a first terminal user based on characteristic information of the first service, and then report the number of first users to a second core network element. Alternatively, the guaranteed bandwidth of the first service can be determined based on the number of first users, and then the guaranteed bandwidth of the first service can be reported to the second core network element. In this way, the experience guarantee when multiple users use the first service simultaneously can be ensured. For example, the bandwidth requirements when multiple users use the first service simultaneously can be ensured, and the accuracy of the QoE results and / or quality difference results obtained when multiple users use the first service simultaneously can also be improved.

[0175] The method provided in the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0176] Figure 4 It is a schematic flow chart of the communication method provided in an embodiment of the present application. Figure 4 The method provided in this application is described from the perspective of the first core network element as an example, but this should not constitute any limitation to this application. Figure 4 The first core network element in the network can also be replaced by a component in the first core network element, such as a chip, a chip system, a processor, etc., or can be replaced by a logic module or software that can realize part or all of its functions, etc. This application does not limit this.

[0177] Among them, the first core network network element can be, for example, a UPF, etc., and this embodiment of the present application does not limit this.

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

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

[0180] Exemplarily, the first service may include services of one or more APPs. For example, 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 include the same type of service for the same type of APP. For example, the first service may include the same service for the following types of APPs: live broadcast APP, game APP, chat APP, etc. Among them, the first service is the live broadcast service of the live broadcast APP, such as the live broadcast APP may include APP#1 and APP#2, and the first service may be the game service of the game APP, which includes APP#3, APP#4, etc. This embodiment of the application does not limit this.

[0182] That is, the first service may include one or more services, or may include a type of service, that is, include multiple services.

[0183] The first core network element can support monitoring of the number of first users of multiple services. During the actual monitoring process, the first core network can calculate characteristic information according to a single service, and then the obtained number of first users is for the number of first users of a single service.

[0184] If a single service corresponds to multiple APPs, characteristic information may be further calculated based on different APPs to determine the number of first users corresponding to the APP.

[0185] For example, a CPE can support six users, two of whom are using the gaming services of a gaming app, three of whom are using the live streaming services of live streaming app #1, and one of whom is using the live streaming services 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 that the first number of users who simultaneously use the game service of the game APP is 2 based on the characteristic information corresponding to the game service of the live broadcast APP#1; the first number of users who simultaneously use the live broadcast service is 3 based on the characteristic information corresponding to the live broadcast service of the live broadcast APP#2; and the first number of users who simultaneously use the live broadcast service is 1 based on the characteristic information corresponding to the live broadcast service of the live broadcast APP#2.

[0187] The first terminal user can provide a hotspot service for at least one user, and the at least one user can use different services after accessing the network through the hotspot of the first terminal user. For example, the at least one user uses the first service at the same time.

[0188] In other words, the first terminal user can provide at least one user with an account for using the first service, that is, at least one user can use the same service through the first account of the first terminal user. The at least one user and the first terminal user can share the same account to use the same service.

[0189] For the network, only the traffic generated by the first end user (i.e., the terminal device or CPE connected to the network and enabling the hotspot) when using the first service is detected. For example, for App#1, the first end user can access App#1 by logging in with the first account, and multiple different users can also access App#1 simultaneously by logging in with the first account. In this case, the network can monitor the traffic generated by the first end user when using the first service.

[0190] In this way, the first core network element cannot directly obtain the number of users who simultaneously use the first service through the first terminal user. In other words, the first core network element cannot know the number of users who actually use 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, and the first number of users is the number of users who use the first service simultaneously through the first terminal user.

[0192] It can be understood that the first number of users can also be called the number of concurrent users who use the first service simultaneously through the first terminal user. The concurrent number of users can be understood as the total number of users who use the first service simultaneously, etc. This embodiment of the present application does not limit this.

[0193] It should also be understood that the number of first users who use the first service simultaneously through the first terminal user can also be referred to as the number of concurrent APP users, that is, the number of concurrent users who use the same or the same type of APP simultaneously through the first terminal user. Among them, APP can correspond to the first service, and the number of first users corresponds to the number of concurrent users. The two are called differently, but the meanings expressed are the same. The number of first users or the number of concurrent APP users can be used interchangeably hereinafter, and should not constitute any limitation on the embodiments of the present application.

[0194] Optionally, the characteristic information includes at least one of 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 information, uplink and downlink messages, or rates.

[0195] Among them, the traffic statistical information can be understood as, for example, the uplink and downlink traffic, total traffic, uplink and downlink traffic ratio, traffic transmitted by the first service during this period, and other information, which is not limited in this embodiment of the present application.

[0196] The first core network element can calculate the derived features of each feature information using different mathematical methods based on the above feature information. Furthermore, the derived features of each feature information can be used to achieve real-time perception of the number of first users through an AI model or algorithm.

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

[0198] It can be understood that the characteristic information includes 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 information, uplink and downlink messages, or at least one of the rates. These are only examples. For example, other types of behavioral characteristics may also be included, etc. The embodiments of the present application are not limited to this.

[0199] In one example, the first core network element implements real-time perception of the number of concurrent users of the first service through an AI model or algorithm based on the number of concurrent flows of users accessing the first service within a period (for example, every 5 seconds (s) as a period), 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 at least one characteristic information in the rate. Through perception, the number of first users who simultaneously use the first service through the first terminal user can be obtained.

[0200] It can be understood that the method for obtaining the number of first users provided in the above step 410 is only an example, but the scope of protection of this application is not limited to this. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, or other feature engineering, models, algorithms, and solutions that can achieve real-time perception of the number of first 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, where the first message includes the number of first users and / or the guaranteed bandwidth of the first service, where the guaranteed bandwidth is determined based on the number of first users.

[0202] In one example, a first core network element may report the number of first users simultaneously using a first service, obtained through perception, to a second core network element, such as an NWDAF, via a first message. Furthermore, the second core network element may obtain a guaranteed bandwidth for n users simultaneously using the first service based on the number of first users and the guaranteed bandwidth for a single user. Where n represents the number of first users, and the guaranteed bandwidth reflects the bandwidth requirement for ensuring a good experience with 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 may obtain the guaranteed bandwidth for n users simultaneously using the first service, i.e., the guaranteed bandwidth for the first service, based on the number of first users simultaneously using the first service and the guaranteed bandwidth for a single user, where n represents the number of first users.

[0205] Furthermore, the first core network element may report the guaranteed bandwidth of the first service to the second core network element via a first message, and provide the second core network element with a recommended guaranteed bandwidth for the first service via the first message. The second core network element may determine the actual guaranteed bandwidth for the first service based on the recommended guaranteed bandwidth for the first service indicated in the first message. The second core network element may be, for example, an NWDAF.

[0206] It can be understood that the method provided in the above step 420 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, but the scope of protection of the present application is not limited to this. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope 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 a first terminal user can simultaneously use the first service. The first core network element can determine the number of users (referred to as the number of first users) who are simultaneously using the first service through the first terminal user based on the characteristic information of the first service, and then report the number of first users to the second core network element. Alternatively, the first core network element can determine the guaranteed bandwidth for the first service based on the number of first users, and then report the guaranteed bandwidth for the first service to the second core network element. In this way, the user experience can be improved when multiple users use the first service simultaneously.

[0208] The following describes in detail the method provided in the embodiments of the present application for different scenarios.

[0209] Scenario 1: A key business assurance solution for VIP users, enabling accurate quality perception and assurance processes in multi-user concurrent scenarios.

[0210] Figure 5 This is another schematic flowchart of the communication method provided in an embodiment of the present application. Figure 5 The method 500 shown is based on Figure 4 Method 400 is provided as a basis for illustrating another processing logic of the communication method. 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 as an example, but this should not constitute any limitation on this application.

[0211] also, Figure 5 The first core network element in the embodiment may also be replaced by a component in the first core network element, such as a chip, a chip system, a processor, etc., or may be replaced by a logic module or software that can implement part or all of its functions; Figure 5 The second core network element in the network element can also be replaced by a component in the second core network element, such as a chip, a chip system, a processor, etc., and can also be replaced by a logic module or software that can realize part or all of its functions; the PCF or AMF can also be replaced by a component in the PCF or AMF, such as a chip, a chip system, a processor, etc., and can also be replaced by a logic module or software that can realize part or all of its functions. This application does not limit this.

[0212] The following description focuses on the steps that are different from the aforementioned method 400. The same steps as those in method 400 and the description of the same terms can be found in the relevant description above and will not be repeated here.

[0213] Exemplarily, the first core network network element may be, for example, a UPF, the second core network network element may be, for example, an NWDAF, and so on, which is not limited in the embodiments of the present application.

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

[0215] See Figure 5 , Figure 5 The method 500 shown may include steps 501 to 515 , and each step in the method 500 is 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 who simultaneously use the first service.

[0217] For example, the second message is a quality difference event subscription request message (exemplarily, it can be a Nupf_EventExposure_Subscribe Request message), and the quality difference event subscription request message can be, for example, a VIP user APPs quality difference event subscription request message.

[0218] When the second core network element sends a poor quality event subscription request message to the first core network element, the second core network element may extend the poor quality event subscription request message with first information for triggering the first core network element to sense the number of first users. In other words, the poor quality event subscription request message may extend the capability of sensing the number of first users of multiple services (or the number of concurrent users).

[0219] For details about the first number of users, the first terminal user, and the first service, please refer to the detailed description in method 400 and will not be repeated here.

[0220] The second message is a VIP user app poor quality event subscription request message. The first terminal user may be a VIP user, and the first service may 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 poor quality events that occur when the VIP user uses a specific app through the second message.

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

[0222] In one example, the first information is the app's concurrent user count perception reporting flag (appConcurrentUserNumFlag). In other words, the app's concurrent user count perception reporting flag is expanded in Nupf_EventExposure_Subscribe. After detecting this first information, the first core network element can sense the app and obtain the first number of users (i.e., concurrent users) who are simultaneously using the app from the same terminal user.

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

[0224] The service can be described as: a network function (NF) service user can subscribe to device-level event information from the first core network element through the service.

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

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

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

[0228] The output parameters of the second message include: mandatory output parameters and optional output parameters.

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

[0230] Optional output parameter: First Related Event Report (if available).

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

[0232] It is understood that, based on the input parameters of the second message, the relevant content requested by the second core network element for subscription can be clarified. Accordingly, based on the output parameters of the second message, it can be determined whether the subscription requested based on the second message is effective.

[0233] Illustratively, through the definitions in Tables 1 to 4 below, the APP concurrent user number perception reporting identification field (ie, the first information field) can be expanded in Nupf_EventExposure_Subscribe.

[0234] As shown in the definition of the CreateEventSubscription type in Table 1, Nupf_EventExposure_Subscribe includes a CreateEventSubscription field.

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

[0236] Table 1 Definition of CreateEventSubscription type

[0237]

[0238] As shown in Table 2, the definition of the UpfEventSubscription type in Table 1, 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, in the definition of the UpfEvent type in Table 2, the UpfEvent field includes a reporting suggestion information (reportingSuggestionInfo) field.

[0242] The data type of the reportingSuggestionInfo field is reporting suggestion information (ReportingSuggestionInformation).

[0243] Table 3 Definition of UpfEvent type

[0244]

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

[0246] Table 4 Definition of ReportingSuggestionInformation type

[0247]

[0248] It can be understood that Table 2 and Table 3 are merely examples. Optionally, the definitions in Table 2 and Table 3 may further include a description of the applicability of each attribute, which is not limited in the embodiments of the present application.

[0249] For the relevant descriptions of the definitions of the Nupf_EventExposure_Subscribe related fields in Tables 1 to 4, please refer to the details 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] Exemplarily, the second core network element may send the second message via a Nupf interface, and correspondingly, the first core network element may receive the second message based on the Nupf interface.

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

[0253] Exemplarily, after receiving the second message, the first core network element may 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 may 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. The 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 method is that the first core network element determines 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 using the first service simultaneously.

[0255] Exemplarily, the first information is an APP concurrent user number perception reporting identifier, and the first service is the first APP. After receiving the second message, the first core network network element can detect the first information carried in the second message (that is, the APP concurrent user number identifier), thereby enabling the first core network network element to have the ability to perceive the APP concurrent user number, and based on the APP concurrent user number perception capability, as well as the number of concurrent flows of users accessing the APP within a period (for example, 5s), the start and end time of each flow in the concurrent flow, the timing relationship between different flows in the concurrent flow, traffic statistics information, and at least one feature information in the uplink and downlink messages or rates, real-time perception is performed through the AI ​​model, thereby obtaining the first number of users (that is, the number of APP concurrent users).

[0256] In other words, after the first core network element detects the first information included in the second message, it can trigger the perception of the number of users who use the first service at the same time.

[0257] For relevant instructions on how 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, please refer to the detailed content of step 410 in method 400, which will not be repeated here.

[0258] One possible implementation method is that the first core network element takes effect according to the local configuration of the first core network element, and determines the first number of 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 perceive the number of users who use the first service at the same time.

[0259] Exemplarily, the first core network element may locally configure the first core network element to sense the number of users simultaneously using the first service. When the local configuration takes effect, the first core network element may determine the number of first users based on the feature information of the first service of the first terminal user.

[0260] In other words, the first core network element can locally configure a capability related to sensing the number of users simultaneously using the first service. After enabling this capability, the first core network element can obtain the number of users through sensing without having to extend the first information in the second message sent by the second core network element. This can reduce signaling overhead.

[0261] For relevant instructions on how 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, please refer to the detailed content of step 410 in method 400, which will not be repeated here.

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

[0263] Exemplarily, the aforementioned second message is a VIP user app poor quality event subscription request message. Correspondingly, the first response message can be, for example, a VIP user app poor quality event subscription response message. That is, the first core network element responds to the second message by sending 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 of the VIP user whose request to monitor the poor quality event when using a specific APP has been accepted.

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

[0266] Exemplarily, after the first core network element determines the first number of users based on the aforementioned step 503, optionally, the method also includes: the first core network element determines the quality difference result and / or QoE result based on a first algorithm, and the input parameters of the first algorithm include the first number of users.

[0267] The first algorithm may be a QoE algorithm (or model) and / or a quality difference judgment algorithm (or model). A QoE result may be obtained based on the QoE algorithm, and a quality difference result may be obtained based on the quality difference judgment algorithm.

[0268] In one example, the parameters related to the first number of users can be converted according to the number of single users, and then the converted parameters can be input as input parameters to the QoE algorithm and / or the quality difference judgment algorithm to determine the quality difference result and / or QoE result, thereby enhancing the QoE algorithm and / or the quality difference judgment algorithm.

[0269] Among them, the method of converting according to the number of single users can be, for example, by calculating the average value, weighted average value, median, etc., which is not limited in the embodiment of the present application.

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

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

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

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

[0274] It can be understood that the above conversion of the relevant parameters corresponding to n users into the relevant parameters corresponding to a single user by calculating the average value is only an example and should not constitute any limitation to the embodiments of the present application.

[0275] In another example, the first number of users is set as characteristic information, which can be annotation information, and then the first number of users is input as an 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] Specifically, when extracting and labeling feature information during QoE evaluation, the first user count is input into the first algorithm as new feature information, indicating that the multiple sets of feature information acquired by the first core network element through perception are based on the same service. This ensures that during model training, each sample includes the concurrent user count feature in addition to the originally collected service flow features, and the concurrent user count is processed accordingly during subsequent tokenization and vectorization.

[0277] Optionally, the first core network element may adjust the first algorithm based on the first number of users. In this way, the first core network element may obtain accurate QoE results and / or quality difference results based on the adjusted first algorithm. The first algorithm may also be an AI model, etc., which is not limited in this embodiment of the present application.

[0278] That is, after the first core network element determines that it has the ability to sense the number of users simultaneously using the first service, it obtains the number of first users through sensing, and can then adjust the QoE algorithm and / or the quality difference judgment algorithm. In this way, the QoE algorithm and / or the quality difference judgment algorithm can also support the expansion of the APP multi-user concurrent scenario.

[0279] Figure 6This is a diagram of the QoE and / or quality difference evaluation algorithm architecture provided by an embodiment of the present application. The QoE and / or quality difference evaluation algorithm architecture includes one of the following modules: 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 the real-time bandwidth usage and determine whether the current communication is congested or idle.

[0281] SA identification: used to identify different service types in the network, for example, the aforementioned first service.

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

[0283] In one possible scenario, the characteristic information may include: uplink rate, downlink rate, uplink round-trip time (RTT), downlink RTT, jitter, packet loss rate, etc. The characteristic information may be obtained by converting the data according to the number of single users.

[0284] In one possible scenario, the feature information may 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 be input into the model as new feature information for training.

[0285] The above parameters are input as input parameters into a business key quality indicator (KQI) model (or algorithm). The KQI model is an example of the above-mentioned first algorithm.

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

[0287] The service KQI model can output QoE results. Taking the live broadcast service as an example, the QoE results may include but are not limited to at least one of the following parameters: bit rate, freeze rate, freeze duration, initial cache duration, etc.

[0288] Furthermore, a QoE score can be performed based on the QoE results output by the service KQI model.

[0289] It can be understood that obtaining accurate QoE results and / or quality difference results based on the above two methods is only an example, but the scope of protection of this application is not limited to this. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, or other messages and processes that can achieve accurate QoE results and / or quality difference results in APP multi-user concurrent scenarios are within the scope of coverage of this patent.

[0290] Furthermore, the first core network element may use the first number of users as an 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, where the first message #1 includes the number of first users and / or the guaranteed bandwidth of the first service, where the guaranteed bandwidth is determined based on the number of first users.

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

[0293] It can be understood that the first message #1 is an example of the first message in the aforementioned method 400. For the relevant description of 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, correspondingly, the first message #1 can be, for example, a VIP user APPs poor quality event notification message (exemplarily, it can be a Nupf_EventExposure_Notify message).

[0295] One possible scenario is that the first message #1 includes the first user number.

[0296] After receiving the first message #1, the second core network element may further determine the guaranteed bandwidth required for the first service under the first number of users 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, and the service can be described as: When an event subscribed to by the NF service consumer second core network element occurs, the first core network element notifies the second core network element of one or more PDU session-related event information through the 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 correlation ID.

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

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

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

[0303] Exemplarily, after receiving the first message #1, the second core network element can return a processing result identifier (for example, "successfully received" or "repeated report", etc.) to the first core network element to inform the first core network element whether the first message #1 reported this time is processed normally.

[0304] Optional output parameters: None. In other words, there are no optional output parameters.

[0305] It can be understood that based on the input parameters of the first message #1, it can be ensured that the event is traceable, etc.

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

[0307] Illustratively, through the definitions in Tables 5 to 9 below, the first user number field for simultaneously using the first service by the first terminal user may be expanded in Nupf_EventExposure_Notify.

[0308] As shown in Table 5, the definition of the NotificationData type, Nupf_EventExposure_Notify includes a NotificationData field, which includes two fields: notification item (notificationItems) and correlation identifier (correlationId). Among them, the data type of notificationItems is array (NotificationItem) (array(NotificationItem)).

[0309] Table 5 Definition of NotificationData type

[0310]

[0311] As shown in Table 6, the definition of the NotificationItem type in Table 5, the NotificationItem field includes a 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 definition of the QosAnalysisInfo type in Table 6, the QosAnalysisInfo field includes an 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 definition in Table 7, the QosInfoType field includes an 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 definition of the QosMonitoringReport type in Table 7, the QosMonitoringReport field includes the APP concurrent user number (appConcurrentUserNum) field, and the data type of the appConcurrentUserNum field is an integer.

[0321] Table 9 Definition of QosMonitoringReport type

[0322]

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

[0324] It can be understood that Table 5, Table 7 and Table 9 are only examples. Optionally, the definitions of Table 5, Table 7 and Table 9 may also include a description of the applicability of each attribute, which is not limited in the embodiments of the present application.

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

[0326] One possible scenario is that the first message #1 includes the guaranteed bandwidth of the first service.

[0327] That is, after determining the number of first 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 number of first users and the guaranteed bandwidth for a single user using the first service. In other words, it can determine the bandwidth that guarantees a good experience for the first service when multiple users access the first service simultaneously.

[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 possible scenario is that the first message #1 includes the number of first users and the guaranteed bandwidth of the first service.

[0330] That is, after determining the number of first 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 number of first users and the guaranteed bandwidth for a single user using the first service. Furthermore, the first core network element can report the determined number of first users and the guaranteed bandwidth for the first service to the second core network element via first message #1.

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

[0332] Exemplarily, the first core network element may determine the quality difference result and / or the QoE result based on the first algorithm adjusted in the aforementioned step 505 .

[0333] For details about the first algorithm and how the first core network element obtains 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 difference subscription request message. In this case, the first message #1 further includes second information, the second information being used to characterize the quality difference result and / or QoE result, and the second information being determined based on the first number of users.

[0335] The first core network element may report the second information representing 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, regarding the definition of the QosInfoType parameter in Table 8, the QosInfoType parameter includes service quality analysis (QOS_ANA), and QOS_ANA indicates that the service quality analysis information (QosAnalysisInfo) is used for inferior information, or in other words, for key service experience assurance.

[0337] The second information may be, for example, the QosInfoType field in Table 8, where the value of the QosInfoType field is QOS_ANA.

[0338] Optionally, the first core network element sends the first message #1, including: the first core network element sends the first message #1 when the number of first terminal users who simultaneously use the first service changes.

[0339] That is, the first message is also used to indicate that the number of users of the first account who simultaneously use the first service has changed.

[0340] The first core network element may continuously monitor the number of users concurrently using the first service. When the first core network element determines, through perception, that characteristic information based on the first terminal user's use of the first service has changed, the first core network element may determine that the number of users concurrently using the first service through the first terminal user has changed. In this case, the first core network element may be triggered to send the first message #1 to the second core network element.

[0341] For example, the first core network element may further determine the number of first users based on the acquired characteristic information of the first service using an AI model or algorithm, and then report the number of first users to the second core network element via the first message #1.

[0342] Optionally, the first core network element sends the first message #1, further comprising: 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 above, the second message is a VIP user APPs poor quality event subscription request message. 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 of the first service.

[0345] One possible scenario is that the first message #1 includes the first user number.

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

[0347] Exemplarily, the second core network element may obtain the guaranteed bandwidth of the first service when multiple users currently use the first service based on the number of first users and the guaranteed bandwidth when a single terminal user uses the first service.

[0348] For example, the guaranteed bandwidth of the first service may 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 is enabled to increase the computing power based on the multiple of the first number of users when calculating the guaranteed bandwidth, thereby providing the effective bandwidth guarantee required by multiple users who use the first service simultaneously through the first terminal user.

[0350] One possible scenario is that the first message #1 includes the guaranteed bandwidth of the first service.

[0351] For example, the second core network element can directly obtain the guaranteed bandwidth for the current multiple users using the first service based on the first message #1. In this way, 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 computing overhead of the second core network element.

[0352] It can be 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 only 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 an ABR based on the first number of users.

[0354] When the number of users using the first service simultaneously through the first terminal is n, multiples of the first user number can also be introduced for processing. For example, the ABR corresponding to the first service can satisfy the following: 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. The PCF policy recommendation request message #1 may carry the first recommended bandwidth for the first service, which is the guaranteed bandwidth for the first service. Accordingly, 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 may push a policy adjustment suggestion 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 the PCF may trigger establishment of a dedicated bearer based on the first recommended bandwidth of the first service carried in the received PCF policy recommendation request message #1.

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

[0359] The PCF can trigger dedicated bearer creation based on the first recommended bandwidth for the first service carried in the PCF policy recommendation request message. Alternatively, when creating a dedicated bearer, the PCF can request GBR bandwidth based on the first recommended bandwidth. This GBR bandwidth, also known as the first recommended bandwidth, satisfies the following conditions: the GBR bandwidth is equal to the first number of users, n, multiplied by the guaranteed bandwidth for a single user using the first service. In other words, when creating a dedicated bearer, the PCF can request GBR bandwidth based on the first number of users, n.

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

[0361] The PCF may generate a policy based on real-time or historical decision results, and send the generated policy to the second core network element via a PCF policy recommendation notification message.

[0362] In step 511, the second core network element calculates available resource data of the access network device based on the dedicated bearer establishment flag.

[0363] For example, the dedicated bearer establishment mark may include a service type identifier, QoS parameter association or resource occupancy record, etc. The second core network element may obtain the available resources of the access network device through calculation based on the above mark.

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

[0365] As time changes, the number of first users who simultaneously use the first service through the first terminal user may change. For example, the number of first users may increase or decrease.

[0366] For example, the first core network element may continuously monitor the number of first users concurrently using the first service. When the first core network element determines through perception that characteristic information based on the first terminal user's use of the first service has changed, it may determine that the number of first users concurrently using the first service through the first terminal user has changed. Based on this, the first core network element may further re-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 number of users is another example of the first number of users. For details about how the first core network element obtains the second number of users based on the characteristic information of the first service, please refer to the detailed description of how the first core network element obtains the first number of users in method 400, which will not be repeated here.

[0368] Optionally, the first core network element may further 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 may 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 may further re-determine the second number of users based on the acquired feature information of the first service using an AI model or algorithm.

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

[0370] In step 513, the first core network element sends a first message #2, which includes the number of second users and / or the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the number of second 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 number of users is another example of the aforementioned first number of users. For details regarding the first message #2 and the second number of users, please refer to the details of the first message and the first number of users in the aforementioned method 400, and will not be repeated here.

[0372] In step 514, the second core network element determines the guaranteed bandwidth of 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. Accordingly, the PCF receives this PCF policy recommendation request message #2.

[0374] PCF policy recommendation request message #2 is an example of PCF policy recommendation request message #1 in the aforementioned step 508 and should not constitute any limitation to the embodiments of the present application.

[0375] For the relevant descriptions of steps 513 to 515, please refer to the detailed contents of steps 506 to 508 in method 500, which 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, PCF, AMF and the first terminal user and SMF (the first terminal user and SMF are in Figure 5 (not shown) interact with each other, thereby achieving the enhancement of the perception and guarantee capability of the first number of users of the first service by the VIP user key service guarantee extension.

[0377] Based on the above technical solution, the first core network element can enhance its ability to perceive the number of users (i.e., the number of first users) simultaneously using the first service through the first terminal user. Information about the number of first users can be added to the first message reported by the first core network element, or information about the guaranteed bandwidth of the first service obtained based on the number of first users can be added. This allows the second core network element to recommend a quality assurance policy based on the guaranteed bandwidth of the first service carried in the first message, or to calculate the guaranteed bandwidth based on the guaranteed bandwidth for a single user using the first service and the number of first users. This ensures a guaranteed experience for the first service.

[0378] Furthermore, when the second core network element sends the second message to the first core network element, it can extend its ability to sense the number of concurrent users of the first service (i.e., the number of first users). Before making a quality assessment based on QoE / KPI, the first core network element can add a process for sensing the number of first users concurrently using the first service. Then, based on the sensed number of first users, the QoE / quality assessment algorithm is adjusted to ensure accurate quality results and / or QoE result reporting. This allows operators to accurately perceive the concurrent user status of the first service in the network based on this sensing function, and achieve precise sensing, assurance, and control under VIP user priority service assurance or differentiated billing and control policies.

[0379] Scenario 2: For experience maps, user perception analysis results, or to ensure visual effects, indicators reflecting the number of concurrent users.

[0380] Figure 7 This is another schematic flowchart of the communication method provided in an embodiment of the present application. Figure 7 The method 700 shown is based on Figure 4 The method 700 is based on the method 400 provided, and another processing logic of the communication method is shown. The method 700 is based on the method 400, and takes the interaction between the first core network element, the second core network element, the first terminal user, the SMF, the PCF and the AMF as an example to describe the method provided by the present application, but this should not constitute any limitation to the present application. In addition, Figure 7 The first core network element in the embodiment may also be replaced by a component in the first core network element, such as a chip, a chip system, a processor, etc., or may be replaced by a logic module or software that can implement part or all of its functions; Figure 7 The second core network element in the embodiment may also be replaced by a component in the second core network element, such as a chip, a chip system, a processor, etc., and may also be replaced by a logic module or software that can implement part 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., and can also be replaced by logic modules or software that can realize part or all of its functions. This application does not limit this.

[0381] The following description focuses on the steps that are different from the aforementioned method 400. The same steps as those in method 400 and the description of the same terms can be found in the relevant description above and will not be repeated here.

[0382] Exemplarily, the first core network element may be a UPF, the second core network element may be an NWDAF, and so on, which is not limited in the embodiments of the present application.

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

[0384] See Figure 7 , Figure 7 The method 700 shown may include steps 701 to 710. Each step in the method 700 is 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 who simultaneously use the first service.

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

[0387] For details about the first number of users, the first terminal user, and the first service, please refer to the detailed content of method 400 and will not be described in detail.

[0388] If the second message is a general user experience receipt subscription request message, the first terminal user may be a general user, and the first service may include different apps (APPs) or different types of apps. The second core network element may obtain service access and experience data of different users through the second message, etc.

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

[0390] In one example, the first information is the appConcurrentUserNumFlag (appConcurrentUserNumFlag). In other words, the appConcurrentUserNumFlag can be extended in the Nupf_EventExposure_Subscribe message (i.e., the second message). This second message format can reuse the second message format used in step 510 of method 500, when the appConcurrentUserNumFlag is extended in the Nupf_EventExposure_Subscribe message.

[0391] For details about the first information and the second message, please refer to the detailed description of step 510 in method 500, which will not be repeated here.

[0392] The second information also includes a Nupf EventType field. As shown in Table 10, the EventType enumeration in Table 3 can include Quality of Service Analysis (QOS_ANA) and Quality of Service Experience (QOS_EXP). QOS_ANA is used for experience analysis reporting, while QOS_EXP is used for service experience assurance.

[0393] Table 10 Nupf EventType enumeration

[0394]

[0395] For the relevant description of the enumeration-related field definitions of Nupf EventType in Table 10, please refer to the details in 3GPPTS 23.502 V19.3.0 (2025-03), which will not be repeated 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] Exemplarily, the second core network element may send the second message via a Nupf interface, and correspondingly, the first core network element may 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 characteristic information of the first service of the first terminal, where the first number of users is the number of users who use the first service simultaneously.

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

[0400] Exemplarily, the aforementioned second message is a normal user experience ticket subscription request message. Correspondingly, the second response message may be, for example, a normal user experience ticket subscription request response message. That is, the first core network element responds to the second message by sending the second response message to the second core network element.

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

[0402] After the first core network element determines the first number of users based on the aforementioned step 703, optionally, the method further includes: the first core network element determines a QoE result based on a first algorithm, where input parameters of the first algorithm include the first number of users.

[0403] For details about the first algorithm and the first core network element obtaining the 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.

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

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

[0406] It can be understood that the 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, which will not be repeated here.

[0407] For the relevant description of the first message #3, please refer to the detailed content of the first message in the aforementioned method 400 and the first message #1 in the method 500, which will not be repeated here.

[0408] Optionally, the second message is a user experience voucher 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 may report the QoE result to the second core network element via the first message #3.

[0410] For example, as mentioned above, regarding the definition of the QosInfoType parameter in Table 8, the QosInfoType parameter includes a service quality experience (QOS_EXP), and QOS_EXP indicates that the service quality analysis information (QosAnalysisInfo) is used for experience information reporting, or for experience analysis reporting.

[0411] For example, the first message may further include the QosInfoType field in Table 8, where the value of the QosInfoType field is QOS_EXP.

[0412] For the relevant descriptions of steps 702 to 706, please refer to the detailed contents 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: an experience map, a user perception analysis result, or a guarantee effect visual interface.

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

[0415] For example, if the first business is APP#1, the number of concurrent users (i.e., the first number of users) who simultaneously access the APP#1 in different time periods can be presented on the generated experience map; for another example, the number of concurrent users (i.e., the first number of users) who simultaneously access the APP#1 in different time periods can be presented in the generated user perception analysis results; for another example, the number of concurrent users (i.e., the first number of users) who simultaneously access the APP#1 in different time periods can be presented in the generated guarantee effect visual interface.

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

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

[0418] In this way, operators can present views or data to the outside world by viewing APP experience analysis maps, APP user perception analysis results, or APP guarantee effect analysis reports, which can reflect the precise number of concurrent users of the APP in different time periods in the network (that is, the number of first users), so as to guide the next step of network optimization, package design, etc.

[0419] In step 708, the first core network element determines the second number of users and / or the guaranteed bandwidth of the first service when the number of first terminal users simultaneously using the first service changes, and the guaranteed bandwidth 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 number of the second users and / or the guaranteed bandwidth of the first service, where the guaranteed bandwidth is determined based on the number of the second users. Correspondingly, the second core network element receives the first message #4.

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

[0422] For the relevant descriptions of step 708 and step 709, please refer to the detailed contents of step 512 and step 513 in the aforementioned method 500, which 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: an experience map, a user perception analysis result, or a guarantee effect visual interface.

[0424] For the relevant description of step 710, please refer to the detailed content of step 707 in the aforementioned method 700, which will not be repeated 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 By interacting with each other (not shown), the perception and guarantee capabilities of the first number of users of the first service can be enhanced based on the experience map, user perception analysis results, or guarantee effect visual interface.

[0426] Based on the above technical solution, the first core network element can enhance its ability to perceive the number of users (i.e., the number of first users) simultaneously using the first service through the first terminal user. Information about the number of first users can be added to the first message reported by the first core network element, or information about the guaranteed bandwidth of the first service obtained based on the number of first users can be added. This allows the second core network element to recommend a quality assurance policy based on the guaranteed bandwidth of the first service carried in the first message, or to calculate the guaranteed bandwidth based on the guaranteed bandwidth for a single user using the first service and the number of first users. This ensures a guaranteed experience for the first service.

[0427] Furthermore, when the second core network element sends the second message to the first core network element, it can expand the perception capability of the number of concurrent users (i.e., the first number of users) required to perceive 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 who simultaneously use the first service, and then adjusts the QoE evaluation algorithm based on the perceived number of first users to ensure that accurate QoE results are reported.

[0428] Furthermore, based on the first core network element having the ability to perceive the number of first users who simultaneously use the first service, the second core network element or report can present the number of first users and experience data accessing the first service collected by the second core network element on the first core network element, thereby generating an experience map of the first service, a guarantee effect analysis report or a guarantee effect visual interface and other related external presentations, which can reflect the precise number of first users who simultaneously use 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: PCC content billing and control solutions implement business processes for different concurrent user numbers, differentiated policies, and billing control.

[0430] Figure 8 This is another schematic flowchart of the communication method provided in an embodiment of the present application. Figure 8 The method 800 shown is based on Figure 4 The method 800 is based on the method 400 provided, and another processing logic of the communication method is shown. The method 800 is based on the method 400 and takes the interaction between the first core network element, NWDAF, the first terminal user, SMF, PCF and AMF as an example to describe the method provided by the present application, but this should not constitute any limitation to the present application. In addition, Figure 8 The first core network element in the embodiment may also be replaced by a component in the first core network element, such as a chip, a chip system, a processor, etc., or may be replaced by a logic module or software that can implement part or all of its functions; Figure 8 The NWDAF, first terminal user, SMF, PCF or AMF can also be replaced by components in the NWDAF, first terminal user, SMF, PCF or AMF, such as chips, chip systems, processors, etc., and can also be replaced by logic modules or software that can realize part or all of its functions. This application does not limit this.

[0431] Among them, the first core network network element can be, for example, a UPF, the SMF or PCF can be, for example, called a second core network network element, and so on. This embodiment of the present application does not limit this.

[0432] See Figure 8 , Figure 8 The method 800 shown may include steps 801 to 811 . Each step in the method 800 is 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] Exemplarily, the SM policy control creation request message may 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] Exemplarily, the SM policy control create request message may be a message requesting a session-related policy from the PCF via an Npcf_SMPolicyControlCreate Request service-based 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 number of users. The first number of users is based on the number of users of the first terminal user who simultaneously use the first service.

[0439] It can be understood that the third message is the same as the second message in the aforementioned method 500 and method 700, is an example of the second message, and should not constitute any limitation to the embodiments of the present application.

[0440] In this case, the PCF can be called 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 determines a second message, 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, and the first number of users is based on the number of users of the first terminal user who simultaneously use the first service.

[0442] For the relevant description of the second message or the third message, please refer to the detailed content of the second message in method 500 and method 700, which will not be repeated here.

[0443] Exemplarily, the second message (ie, the third message) may be, for example, an SM policy control create response (exemplarily, an Npcf_SMPolicyControl Create Response message), and the second message includes the first information.

[0444] One possible scenario is that the first information is an APP concurrent user number perception reporting flag (appConcurrentUserNumFlag).

[0445] That is, a new APP concurrent user number perception reporting identification field is added to the SM policy control creation response determined by the PCF, which is used to activate the perception function of the number of users who simultaneously use the first service on the first core network network element.

[0446] For the relevant content of the first information being the APP concurrent user number perception reporting identifier, please refer to the detailed content of the first information in step 501 in method 500, which will not be repeated here.

[0447] In a possible case, the first information includes a policy and charging control matching rule, in which the number of at least one candidate user who simultaneously uses the first service corresponds one-to-one to at least one policy and charging control.

[0448] That is, the SM policy control creation response determined by the PCF includes a policy and charging control matching rule. In the policy and charging control matching rule, 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 charging control matching rule, "APPId=1" corresponds to policy and charging control #1; and "APPId=2" corresponds to policy and charging control #2.

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

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

[0452] In this way, differentiated strategies and billing control can be implemented under different numbers of concurrent APP users (that is, the first number of users), thereby achieving differentiated management.

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

[0454] The PCF may send the third message to the SMF via the N7 interface. Accordingly, the SMF may receive the third message based on the N7 interface, where the third message 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 simultaneously use the first service.

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

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

[0458] Optionally, the SMF may 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 a second message, the second message includes first information, and 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 simultaneously use the first service.

[0460] For relevant descriptions of the second message, please refer to the detailed content of the second message in method 500 and method 700, which will not be repeated here.

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

[0462] Optionally, the second message includes first information, the first information includes a policy and charging control matching rule, and the policy and charging control matching rule contains a one-to-one correspondence between at least one candidate user number who simultaneously uses the first service and at least one policy and charging control.

[0463] For details about the first information, please refer to the detailed description 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 may send the second message to the first core network element via the N4 interface. Correspondingly, the first core network element may receive the second message based on the N4 interface.

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

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

[0468] For the relevant descriptions of steps 808 to 809, please refer to the detailed contents of steps 503 and 505 in method 500, which will not be repeated here.

[0469] Optionally, the method further includes: the first core network element determining a first policy and charging control according to the first number of users, the first policy and charging control being a policy and charging control corresponding to the first number of users in the policy and charging control matching rule.

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

[0471] The first core network element may determine, based on the first number of users being n, that the policy and charging control corresponding to the first number of users is the first policy and charging control through the corresponding relationship in the policy and charging control matching rule.

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

[0473] For relevant descriptions on the first core network element determining the guaranteed bandwidth of the first service 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 the relevant description of the first core network element determining the ABR 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, the first message including the guaranteed bandwidth of the first service, the guaranteed bandwidth being determined based on the number of the first users. Correspondingly, the PCF receives the first message.

[0476] After receiving the first message, the PCF may apply for GBR bandwidth based on the guaranteed bandwidth of the first service included in the first message, or based on the number of first users, in a scenario where creation of a dedicated bearer is triggered.

[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 (not shown) interact with each other to enhance the perception and control capabilities of the first number of users of the first service for key service management.

[0478] Based on the above technical solution, operators can customize packages by defining a list of key apps that can be used by multiple users concurrently and occupy a large amount of wireless resources. They can implement differentiated management or billing strategies under different concurrent user specifications of apps, thereby generating new package revenue for operators or reducing the occupation of such users or wireless resources.

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

[0480] It should also be understood that in addition to the interactive architecture and process for expanding the perception of the number of concurrent APP users and differentiated strategies for solutions such as key business guarantee for VIP users, visual experience map / guarantee effect, and concurrent number control or billing of key businesses under the 5G or 5.5G network architecture provided in the above-mentioned methods 400, 500, 700, and 800, other related functional entities, processes, and solutions that can realize differentiated statistics, billing, control, guarantee, optimization, and other functions based on the number of concurrent APP users are all within the scope of coverage of this patent.

[0481] Figure 9 This is another network system architecture diagram provided by the embodiment of this application. Figure 1 The difference between the network system architecture shown in the figure is that PCF can add the function of issuing APPA concurrent user number control policy; UPF (for example, PDU Session Anchor UPF 1 (PSA-UPF1)) can add the functions of service perception, APP concurrent user number identification and quality difference perception, and also add the function of APP concurrent user number control, and can also report the number of APP concurrent users and optimize the evaluation of QoE results and / or quality difference results; NWDAF can add the functions of quality difference guarantee policy recommendation and guaranteed bandwidth calculation, and also add the function of visualizing QoE results and / or quality difference results under multiple concurrent services.

[0482] It can be understood that the main deployment form of the method provided in the embodiment of the present application can be to enhance the perception capability of the number of first users of different types of first services (or the number of concurrent users of APP) on UPF, and then expand the support for the perception and control capability of the number of first users of the first service in key service assurance scenarios, experience maps / visualization of assurance effects, key service concurrent number management or billing and other solutions. That is, the perception and strategy of the number of concurrent users of APP can be presented in the corresponding interface definition, configuration data, and solution information.

[0483] The UPF can be defined to support the ability to sense the number of concurrent app users. This control or description of this sensing function can also be included in the network element configuration or function description in the product manual. This is the primary method for obtaining evidence of infringement. Additionally, the NWDAF or other data analysis and visualization network elements can also describe this sensing function in their VIP user key service assurance plans or visualization function descriptions. Carrier network equipment can also obtain evidence of infringement through product manuals, solution materials, and interface definitions and interaction messages between the UPF and NWDAF or other surrounding network elements.

[0484] The method provided by the embodiment of the present application is described in detail above with reference to a plurality of drawings. The device provided by the embodiment of the present application is described below with reference to the drawings.

[0485] Figures 10 and 11 Schematic block diagram of possible devices provided for embodiments of the present application. These devices can be used to implement the functions of the first core network element or the second core network element in the above method embodiment, and thus can also achieve the beneficial effects of the above method embodiment. In the embodiment of the present application, the device can 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 may also be a component (such as a chip, a chip system, a processor, etc.) configured in the first core network element or the second core network element, or may be a logic module or software that can implement part or all of the functions of the first core network element or the second core network element.

[0486] The present application provides a device such as Figure 10 As shown, the device 1000 includes a transceiver unit 1010 and a processing unit 1020 .

[0487] One possible design is that the device 1000 is used to implement the above Figure 4 、 Figure 5 、 Figure 7 or Figure 8 The function of the first core network element in the method embodiment shown in FIG. 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] Exemplarily, the processing unit 1020 is used to determine the first number of users based on the characteristic information of the first service of the first terminal user, where the first number of users is the number of users who simultaneously use the first service; the transceiver unit 1010 is used to send a first message, where the first message includes the first number of users and / or the guaranteed bandwidth of the first service, where the guaranteed bandwidth is determined based on the first number of users.

[0489] Optionally, the characteristic information includes at least one of 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 information, uplink and downlink messages, or rates.

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

[0491] Optionally, the processing unit 1020 is also used 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 network element to perceive the number of users who simultaneously use the first service; or, based on the local configuration of the first core network element, the first number of users is determined based on the characteristic information of the first service of the first terminal user, and the local configuration is used to configure the first core network element to perceive the number of users who simultaneously use the first service.

[0492] Optionally, the second message is a quality difference event subscription request message, and the first message further includes second information, where the second information is used to characterize the quality difference 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 voucher subscription request message, and the first message further includes a QoE result, which is determined based on the first number of users.

[0494] Optionally, when the number of users of the first terminal who simultaneously use the first service changes, the transceiver unit 1010 is further configured to send the first message.

[0495] Optionally, the processing unit 1020 is further configured to determine the quality difference result and / or the 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 billing control matching rule, in which at least one candidate user number who simultaneously uses the first service corresponds one-to-one with at least one policy and billing control. The processing unit 1020 is also used to determine a first policy and billing control based on the first number of users, and 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 rule.

[0497] One possible design is that the device 1000 is used to implement the above Figure 4 、 Figure 5 、 Figure 7 or Figure 8 The function of the second core network element in the method embodiment shown in FIG. For example, the device 1000 may correspond to Figure 4 、 Figure 5 、 Figure 7 or Figure 8 The second core network element in the embodiment of the present invention, wherein: Figure 8 The second core network element is, for example, Figure 8 The SMF or PCF in the device 1000 can be, for example, the aforementioned second core network element.

[0498] Exemplarily, the processing unit 1020 is used to determine a second message, which includes first information, and the first information is used to trigger the first core network element to perceive the first number of users, and the first number of users is based on the number of users of the first terminal user who simultaneously use 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 receipt subscription request message.

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

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

[0502] Optionally, the second message is a quality difference event subscription request message, and the first message further includes second information, where the second information is used to characterize the quality difference 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 voucher subscription request message, and the first message further includes a QoE result, which is determined based on the first number of users.

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

[0505] Optionally, the first message is further used to indicate a change in the number of users of the first account who simultaneously use the first service.

[0506] Optionally, the processing unit 1020 is further configured to determine an 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, where the third message includes the first information.

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

[0509] Optionally, the first information includes a policy and charging control matching rule, in which at least one number of candidate users based on the first terminal user simultaneously using the first service corresponds to at least one policy and charging control.

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

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

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

[0513] It should also be understood that the transceiver unit in communication device 1000 may also be referred to as a communication unit. The 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. The specific embodiment may depend on whether the above-mentioned solution executed by device 1000 includes both transmitting and receiving actions. The receiving unit may be used to perform the receiving action in the above-mentioned solution, and the transmitting unit may be used to perform the transmitting action in the above-mentioned solution.

[0514] It is understandable that the division of units in the above-mentioned device is merely a division of logical functions, and each function may correspond to a functional unit, or two or more functions may be integrated into one functional unit. In actual implementation, all or part of the units may be integrated into one physical entity, or distributed across different physical entities. In addition, the above-mentioned functional units may be implemented in the form of hardware, software, or a combination of hardware and software. Whether a function is executed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0515] Figure 11 This is another schematic block diagram of the device provided in the embodiment of the present application. Figure 11 As shown, device 1100 includes one or more processors 1110. Processor 1110 can be a general-purpose processor or a dedicated processor. For example, it can be 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 a device (such as a vehicle or chip), execute software programs, and process software program data.

[0516] Optionally, in one design, the processor 1110 may include a computer program (also referred to as code or instructions), which may be executed on the processor 1110 to cause the apparatus 1100 to perform the method performed by the first core network element or the second core network element in the above method embodiment. In another possible design, the apparatus 1100 includes a circuit ( Figure 11 (not shown) the circuit is used to implement the functions of the first core network element or the second core network element in the above method embodiment.

[0517] For example, the processor 1110 may be configured to execute a computer program in the memory to implement Figure 4 、 Figure 5 、 Figure 7 or Figure 8 The steps are performed by the first core network element or the second core network element in the method embodiment shown in the shown embodiment.

[0518] Optionally, the device 1100 may include one or more memories 1120 on which a computer program (sometimes also referred to as code or instructions) is stored. The program can be run on the processor 1110, so that the device 1100 executes the method executed by the first core network element or the second core network element in the above embodiment.

[0519] Optionally, data may be stored in the processor 1110 and / or the memory 1120. The processor and the memory may be provided separately or integrated together.

[0520] Optionally, the apparatus 1100 may further include a communication interface 1130. The processor 1110 may also sometimes be referred to as a processing unit, and controls the apparatus (e.g., the first core network element or the second core network element). The communication interface 1130 may also sometimes be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, and is configured to implement the transceiver functions of the apparatus. For example, the communication interface 1130 may be configured to receive the first message.

[0521] Optionally, the apparatus 1100 further 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 may be a transceiver or an input / output interface.

[0522] When the device 1100 is used to implement Figure 4 、 Figure 5 、 Figure 7 or Figure 8 When performing the method shown, the processor 1110 may be used to execute the functions of the processing unit 1020, and the communication interface 1130 may be used to execute the functions of the transceiver unit 1010. Whether the communication interface 1130 is used for sending or receiving may depend on whether the device 1100 is used to perform a sending action or a receiving action in the solution executed by the device 1100.

[0523] When the apparatus 1100 is a chip implemented in a first core network element, the chip implements the functions of the first core network element in the method embodiments described above. The chip of the first core network element receives a signal from another module (e.g., a radio frequency module or antenna) within the first core network element. This signal may be sent from a second core network element to the first core network element. Alternatively, the chip of the first core network element sends a signal to another module (e.g., a radio frequency module or antenna) within the first core network element. This signal may be sent from the first core network element to the second core network element.

[0524] When the apparatus 1100 is a chip used in a second core network element, the chip implements the functions of the second core network element in the method embodiment. The chip of the second core network element receives a signal from another module in the second core network element, where the signal may be sent from the first core network element to the second core network element; or the chip of the second core network element sends a signal to another module in the second core network element, where the signal may be sent from the second core network element to the first core network element.

[0525] It is understood that when the apparatus 1100 is a first core network element or a second core network element, the communication interface 1130 may be a transceiver, specifically including a transmitter and a receiver, where the transmitter is used to transmit signals and the receiver is used to receive signals. When the apparatus 1100 is a chip applied to the first core network element or the second core network element, the communication interface 1130 may be an input / output circuit, where the input circuit may be used for receiving and the output interface may be used for transmitting.

[0526] Optionally, the device 1100 further includes a power supply circuit, which can be used to supply power to the device 1100 .

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

[0528] The processors described above may 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. A general-purpose processor may be a microprocessor or any conventional processor.

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

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

[0531] The present application also provides a chip system, which includes 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 one of the above method embodiments, for example, sending, receiving or processing the information involved in the above method.

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

[0533] The chip system can be composed of chips, or can include chips and other discrete devices.

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

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

[0536] The present 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 through software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product may include one or more computer instructions. When loaded and executed on a computer, the computer program instructions fully or partially generate the processes or functions described in the embodiments of the present application. 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, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium accessible by 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 magnetic media (e.g., floppy disk, hard disk, magnetic disk), optical media (e.g., DVD), or semiconductor media (e.g., solid-state drive (SSD)).

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

[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, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0541] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of the solution 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 can essentially or partially be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method of each embodiment of this application. The aforementioned storage medium includes: USB flash drives, mobile hard drives, read-only memories, random access memories, magnetic disks, optical disks, and other media that can store program code.

Claims

1. A communication method, characterized in that: Applied to a first core network element, the method includes: Determining a first number of users based on characteristic information of a first service of a first terminal user, where the first number of users is the number of users who simultaneously use the first service; A first message is sent, where the first message includes the number of the first users and / or a guaranteed bandwidth for the first service, where the guaranteed bandwidth is determined based on the number of the first users.

2. The method according to claim 1, characterized in that The characteristic information includes at least one of 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 information, uplink and downlink messages, or rates.

3. The method according to claim 1 or 2, characterized in that The method further comprises: A second message is received, where the second message is a quality difference event subscription request message, or the second message is a user experience ticket subscription request message, or the second message is a session establishment request message.

4. The method according to claim 3, characterized in that The determining the number of first users based on the feature information of the first service of the first terminal user includes: determining the number of first users based on the first information in the second message and based on 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 According to the local configuration of the first core network element, the number of first users is determined 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 perceive the number of users who use the first service at the same time.

5. The method according to claim 3, characterized in that The second message is a quality difference event subscription request message, and the first message further includes second information, where the second information is used to characterize the quality difference result and / or the service experience quality QoE result, and 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 ticket subscription request message, and the first message further includes a service quality of experience (QoE) result, where the QoE result is determined based on the first number of users.

7. The method according to claim 5 or 6, characterized in that The sending of the first message includes: When the number of users of the first terminal who simultaneously use the first service changes, the first message is sent.

8. The method according to claim 5 or 6, characterized in that The method further includes determining a quality difference result and / or a 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 a policy and charging control matching rule, the number of at least one candidate users who simultaneously use the first service in the policy and charging control matching rule corresponds one-to-one to at least one policy and charging control, and the method further includes: A first policy and charging control is determined according to the first number of users, where 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 rule.

10. A communication method, characterized in that: Applied to a second core network element, the method includes: Determine a second message, where the second message includes first information, where the first information is used to trigger a first core network element to sense a first number of users, where the first number of users is based on the number of users of the first terminal user who simultaneously use the first service; The second message is sent.

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 ticket subscription request message.

12. The method according to claim 10 or 11, characterized in that The method further comprises: A first message is received, where the first message includes the number of the first users and / or a guaranteed bandwidth for the first service, where the guaranteed bandwidth is determined based on the number of the first users.

13. The method according to claim 12, characterized in that The second message is a quality difference event subscription request message, and the first message further includes second information, where the second information is used to characterize the quality difference result and / or the service experience quality QoE result, and 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 ticket subscription request message, and the first message further includes a service quality of experience (QoE) result, where the service quality of experience (QoE) result 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: an experience map, a user perception analysis result, or a guarantee effect visual interface.

16. The method according to claim 15, characterized in that The first message is also used to indicate a change in the number of users of the first terminal who simultaneously use the first service.

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

18. The method according to claim 16 or 17, characterized in that The method further comprises: An adaptive bit rate ABR is determined based on the first number of users.

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: A third message is received from a policy control function network element, where the third message includes the first information.

20. The method according to claim 10, wherein The second core network element is a policy control network element.

21. The method according to claim 19 or 20, characterized in that The first information includes a policy and charging control matching rule, in which at least one number of candidate users based on the first terminal user using the first service simultaneously corresponds to at least one policy and charging control.

22. A communication device, characterized in that: The method comprises a module for implementing the method according to any one of claims 1 to 9, or comprises a module for implementing the method according to any one of claims 10 to 21.

23. A communication device, characterized in that: The device comprises one or more processors configured to execute computer programs or instructions in a memory, so that the communication device performs the method according to any one of claims 1 to 9, or the method according to 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, the method according to any one of claims 1 to 9 is executed, or the method according to any one of claims 10 to 21 is executed.

25. A computer program product, characterized in that The invention comprises a computer program which, when being executed, causes the method according to any one of claims 1 to 9 to be performed, or causes the method according to any one of claims 10 to 21 to be performed.

Images