Communication method and apparatus

Abstract

Embodiments of the present application provides a communication method and apparatus, used for improving the user experience. In the present application, a plurality of experience levels mapped to different communication configurations are predefined, and a terminal device can display an icon corresponding to an experience level, so that a user can feel differentiated communication experience in real time, and user's perceived availability to differentiated experience is enhanced.

Description

A communication method and apparatus

[0001] Cross Reference to Related Applications

[0002] This application claims priority to the Chinese Patent Application No. 202411017552.3, filed on July 26, 2024, and entitled "A communication method and apparatus", the content of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application relates to the field of communication technology, and in particular to a communication method and apparatus. BACKGROUND

[0004] Providing differentiated quality experience services for users with different needs is an important direction for the future long-term evolution of wireless communication technology. High-quality experience can improve user recognition of services and applications, and enhance the value of the operator's brand. In particular, by providing precise differentiated services for different user groups, the quality of service experience can be guaranteed, which can promote the revenue of operators and bring impetus for operators to continuously enhance network functions.

[0005] Currently, differentiated services are provided for different user groups by allocating different resources to users of different levels or priorities by the network side according to quality of service (QoS) indicators / ToC slices and other factors. However, for users, since most users do not understand QoS indicators / ToC slices and other factors, users cannot intuitively feel the difference in resources allocated by the network side, resulting in poor user experience. SUMMARY

[0006] The communication method and apparatus provided by the embodiments of the present application are used to improve user experience.

[0007] In a first aspect, the present application provides a communication method. The execution subject of the method can be a terminal device, or a chip or circuit on the terminal device side. Taking the terminal device as an example, the method comprises: displaying an icon corresponding to a first experience level, the first experience level being an experience level of the terminal device, an experience level of a user using the terminal device, or an experience level of a first service running on the terminal device; wherein different experience levels are mapped to different communication configurations.

[0008] The present application predefines a plurality of experience levels, the plurality of experience levels are mapped to different communication configurations, and the terminal device can display an icon corresponding to an experience level, so that the user can feel the differentiated communication experience in real time, and the user's sense of availability of differentiated experience is enhanced. In addition, by standardizing the experience level, the credibility of user experience can be enhanced, thereby further enhancing user experience.

[0009] In a possible design, the first message is received, and the first message is used to indicate that the access network device or the core network device supports or enables the first service, or the first message indicates that the access network device or the core network device enables the first service for a terminal device or a user using the terminal device or a first service running on the terminal device; wherein the first service is configured with a corresponding communication configuration for an experience level. Through the foregoing design, the communication behaviors of the terminal side and the network side can be aligned, and therefore the user experience can be further enhanced.

[0010] In a possible design, the method further includes: receiving first information, the first information being used to indicate a communication configuration configured for the terminal device, wherein the communication configuration indicated by the first information meets the communication configuration corresponding to the first experience level. Through the foregoing design, the accuracy of the displayed experience level can be improved.

[0011] In a possible design, the method further includes: receiving a second message, the second message carrying experience level information, and the experience level information indicating the first experience level. Through the foregoing design, the user can obtain the experience level information, and therefore the user experience can be enhanced.

[0012] In a possible design, the method further includes: sending a third message, the third message being used to request to add or modify (for example, increase) the experience level of the terminal device or the experience level of a user using the terminal device or the experience level of a first service running on the terminal device. Through the foregoing design, the user can experience the differentiated communication experience in real time, and the flexibility can be increased.

[0013] In a possible design, the method further includes: displaying a first prompt, the first prompt being used to inquire whether to add or modify (for example, increase) the experience level of the terminal device or the experience level of a user using the terminal device or the experience level of a first service running on the terminal device.

[0014] In a possible design, the sending of the third message includes: in response to a first operation of the user, the third message is sent, and the first operation is used to confirm to add or modify (for example, increase) the experience level of the terminal device or the experience level of a user using the terminal device or the experience level of a first service running on the terminal device. Through the foregoing, the user experience can be further increased.

[0015] In a possible design, before the third message is sent, the method further includes: determining that a service quality of the terminal device or the first service does not meet a requirement of the user, or the service quality of the terminal device or the first service is less than or equal to a threshold value. Through the foregoing, the user experience can be further increased.

[0016] In a possible design, the method further includes: receiving a fourth message, where the fourth message is used to indicate that the experience level of the terminal device or the experience level of a user using the terminal device or the experience level of a first service running on the terminal device is added or modified (for example, improved). Through the above, the user experience can be further increased.

[0017] In a possible design, the method further includes: obtaining information of a first service, where the information of the first service includes communication configurations corresponding to N experience levels respectively, N is an integer greater than 0, and the first experience level is one of the N experience levels; and the first service is configured with corresponding communication configurations according to the experience level, and the information of the first service is preconfigured or is from an access network device or a core network device.

[0018] In a second aspect, the present application provides a communication method, and an execution subject of the method can be a network device or a chip or circuit at a network device side. The network device can be an access network device or a core network device. Taking the network device as an example, the method includes: sending a second message or first information, where the second message carries experience level information, the experience level information indicates an experience level of a terminal device or an experience level of a user using the terminal device or an experience level of a service running on the terminal device, and the first information is used to indicate a communication configuration configured for the terminal device, where the communication configuration indicated by the first information meets a communication configuration corresponding to the experience level of the terminal device or the experience level of the user using the terminal device or the experience level of the service running on the terminal device.

[0019] Through the above, the user can obtain the experience level information, and thus the user experience can be enhanced.

[0020] In a possible design, the method further includes: sending a first message, where the first message is used to indicate that the access network device or the core network device supports or enables a first service, or the first message indicates that the access network device or the core network device enables the first service for the terminal device or the user using the terminal device or the service running on the terminal device; and the first service is configured with corresponding communication configurations according to the experience level. Through the above design, the communication behaviors at the terminal side and the network side can be aligned, and thus the user experience can be further enhanced.

[0021] In a possible design, the method further includes: sending information of a first service, where the information of the first service includes communication configurations corresponding to N experience levels respectively, N is an integer greater than 0, and the experience level of the terminal device or the experience level of a user using the terminal device or the experience level of a service running on the terminal device is one of the N experience levels; and the first service is configured with corresponding communication configurations according to the experience level.

[0022] In a possible design, the method further includes: receiving a third message, where the third message is used to request to add or modify (for example, increase) the experience level of the terminal device or the experience level of the user using the terminal device or the experience level of the service running on the terminal device. Through the above, the user experience can be further increased.

[0023] In a possible design, before receiving the third message, the method further includes: determining that the service quality of the terminal device or the first service does not meet the user requirement, or the service quality of the terminal device or the first service is less than or equal to a threshold value; and sending a fourth message, where the fourth message is used to indicate to add or modify (for example, increase) the experience level / communication configuration of the first service. Through the above, the user experience can be further increased.

[0024] The method in the above first aspect and the method in the above second aspect can be designed in the following manner.

[0025] In a possible design, the communication configuration includes at least one of the following: slice resource, QoS configuration, QoE configuration, subnet resource, and resource scheduling policy.

[0026] In a possible design, the slice resource includes at least one of the following: slice resource of an access network, slice resource of a core network, and slice resource of a transport network.

[0027] In a possible design, the slice resource of the access network includes at least one of the following: number of dedicated resource blocks (RBs), low-frequency carrier priority enabling, carrier-specific enabling, and time-domain scheduling priority enabling.

[0028] In a possible design, the slice resource of the core network includes at least one of the following: exclusive virtual network function (VNF) network element, VNF network element shared by partial slice resources, and VNF network element shared by all slice resources.

[0029] In a possible design, the slice resource of the transport network includes at least one of the following: transport resource of the transport network, segment routing transport profile (SR-TP), SR-TP operation administration and maintenance (OAM) detection technology, and re-routing protection.

[0030] In a possible design, the QoS configuration includes at least one of the following: the QoS configuration can include at least one of the following: a QoS identifier, an allocation and retention priority (ARP), a guaranteed flow bit rate (GFBR), a maximum flow bit rate (MFBR), an aggregate maximum bit rate (AMBR), a reflective QoS attribute (RQA), a notification control, a maximum packet loss rate.

[0031] In a possible design, the QoS identifier is a QoS class identifier (QCI) or a 5G QoS identifier (5QI).

[0032] In a possible design, the QOE configuration includes at least one of the following: an uplink guaranteed latency, a downlink guaranteed latency, an uplink guaranteed rate, a downlink guaranteed rate, a reliability guarantee, a packet loss rate guarantee, a guaranteed jitter, a task success rate, a service success rate, a guaranteed code rate, a definition, a frame rate, a resolution, an operation response time, a call setup latency, a handover response latency, a bidirectional end-to-end latency.

[0033] In a possible design, the resource scheduling strategy includes at least one of the following: preferentially configuring a large number of resource block (RB) resources in one scheduling time unit, configuring at least M RB resources in one scheduling time unit, preferentially using a low-order modulation and coding format in one scheduling time unit, and using a modulation and coding format not higher than X in one scheduling time unit, where M is an integer greater than 0, and X is a predefined modulation and coding format or a network-configured modulation and coding format threshold.

[0034] In a possible design, the experience level is one or more of the following: a slice level, a QoS guarantee level, a QoE guarantee level, and a subnet level.

[0035] In a third aspect, the present application also provides a communication apparatus, which has any of the methods provided in the first aspect. The communication apparatus can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0036] In a possible implementation, the communication apparatus includes a processor configured to support the communication apparatus to perform the corresponding functions of the terminal device in the above-mentioned method. For example, the processor implements any of the methods provided in the first aspect above by means of a logic circuit or by executing code instructions. The communication apparatus can further include a memory, which can be coupled to the processor, and which stores program instructions and data necessary for the communication apparatus. Optionally, the communication apparatus further includes an interface circuit, which is configured to support the communication apparatus to communicate with other devices such as network devices, for example, the interface circuit is configured to receive signals from other communication apparatuses outside the communication apparatus and transmit the signals to the processor, or transmit signals from the processor to other communication apparatuses outside the communication apparatus.

[0037] In a possible implementation, the communication apparatus includes corresponding functional modules for implementing the steps in the above-mentioned method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0038] In a possible implementation, the structure of the communication apparatus includes a processing unit and a communication unit, which can perform the corresponding functions in the above-mentioned method examples, and the details are described in the methods provided in the first aspect, which will not be repeated here.

[0039] In a possible implementation, the structure of the communication apparatus includes a processing unit and a communication unit, which can perform the corresponding functions in the above-mentioned method examples, and the details are described in the methods provided in the first aspect, which will not be repeated here.

[0040] In a possible implementation, the communication apparatus includes a processor configured to support the communication apparatus to perform the corresponding functions of the network device in the above-mentioned method. For example, the processor implements any of the methods provided in the second aspect above by means of a logic circuit or by executing code instructions. The communication apparatus can further include a memory, which can be coupled to the processor, and which stores program instructions and data necessary for the communication apparatus. Optionally, the communication apparatus further includes an interface circuit, which is configured to support the communication apparatus to communicate with other devices such as terminal devices, for example, the interface circuit is configured to receive signals from other communication apparatuses outside the communication apparatus and transmit the signals to the processor, or transmit signals from the processor to other communication apparatuses outside the communication apparatus.

[0041] In a possible implementation, the communication apparatus includes respective function modules for implementing the steps in the above method. The functions can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0042] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method of the second aspect, which will not be repeated here.

[0043] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method of the second aspect, which will not be repeated here.

[0044] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method of the second aspect, which will not be repeated here.

[0045] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method of the second aspect, which will not be repeated here.

[0046] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method of the second aspect, which will not be repeated here.

[0047] In a possible implementation, the communication apparatus includes a processing unit and a communication unit in its structure, which can perform the corresponding functions in the above method examples, and the details are described in the method of the second aspect, which will not be repeated here.

[0048] The technical effects that can be achieved by the technical solutions of any one of the above third to ninth aspects can be described with reference to the technical effects that can be achieved by the technical solutions of the first aspect, and repeated descriptions will not be repeated. BRIEF DESCRIPTION OF DRAWINGS

[0049] FIG. 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present application;

[0050] FIG. 2 is a schematic diagram of the protocol stack of a network device according to an embodiment of the present application;

[0051] FIG. 3 is a schematic diagram of the architecture of an O-RAN system according to an embodiment of the present application; FIG. 3 is a schematic diagram of the architecture of an O-RAN system according to an embodiment of the present application;

[0052] FIG. 4 is a diagram of network element function division and protocol layer structure of an O-RAN device according to an embodiment of the present application;

[0053] FIG. 5 is a flow diagram of a communication method according to an embodiment of the present application;

[0054] FIG. 6 is a diagram of a structure of a communication apparatus according to an embodiment of the present application;

[0055] FIG. 7 is a diagram of a structure of a communication apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the drawings.

[0057] In the following, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0058] 1. Quality of experience (QoE) is the comprehensive subjective feeling of a user on the quality and performance (including effectiveness and availability, etc.) of a device, network and system, application or service.

[0059] 2. Quality of service (QoS) can be understood as a key performance indicator (KPI) performance indicator of data transmission. QoS includes indicators such as network delay, jitter, bandwidth, error code, etc.

[0060] In the embodiments of the present application, "when", "if" and "whether" all refer to that the device will make corresponding processing under certain objective circumstances, and are not limited to time, and do not require the device to have a judgment action when implemented, nor mean that there are other limitations. Unless otherwise specified, "if" and "whether" can be replaced, "when" and "in the case of" can be replaced. "When" and "if" / "whether" can be replaced.

[0061] In the embodiments of the present application, "at least one" means one or more, and "multiple" means two or more. The "and / or" describes the association relationship of the associated objects, which means that there can be three kinds of relationships, for example, A and / or B can represent: A exists alone, A and B exist together, and B exists alone, where A and B can be singular or plural. The character " / " generally represents an "or" relationship between the associated objects before and after it. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b and (or) c can mean: a exists alone, b exists alone, c exists alone, a and b exist together, b and c exist together, a and c exist together, and a, b and c exist together, where a, b and c can be single or multiple.

[0062] In addition, unless otherwise stated, the ordinal numbers mentioned in the embodiments of the present application are used to distinguish a plurality of objects, and are not used to limit the size, content, order, time sequence, priority or importance of the plurality of objects.

[0063] The background art related to the present application will be introduced first as follows.

[0064] With the rapid development of 5G services, users can experience a significant increase in data transmission rates compared to previous communication systems, and most consumers can experience an improvement in service experience due to high speed. Better precision and differentiation of quality experience services for different needs of users is an important direction for future long-term evolution of wireless communication technology.

[0065] High-quality experience can improve user recognition of services and applications and enhance the value of the operator's brand. In particular, by providing precise differentiated services for different user groups and ensuring service experience quality, operators can increase revenue and continuously enhance network functions.

[0066] Currently, differentiated services are provided for different user groups by the network side according to QoS indicators / ToC slices and other factors to allocate different resources for users of different levels or priorities. For example, an operator can divide users into gold medal users, silver medal users, bronze medal users, etc. The operator can allocate QoS parameters corresponding to a standard QoS class identifier (QCI) 6 to gold medal users, and allocate a priority with an allocation and retention priority (ARP) of 1 or 2, so that gold medal users can obtain better service experience. However, for users, most users do not understand QoS indicators / ToC slices and other factors, which leads to the fact that users cannot intuitively feel the difference in resources allocated by the network side, and the user experience is poor.

[0067] Based on this, the embodiments of the present application provide a communication method and device for improving user experience. The method and device are based on the same technical concept. Since the principles of the method and device for solving problems are similar, the implementation of the device and the method can be mutually referred to, and the repeated parts will not be described again.

[0068] The communication method provided by the present application can be applied to a communication system, which can be a third generation partnership project (3GPP) related communication system. For example, the communication system can be a long term evolution (LTE) system, a 5th generation (5G) mobile communication system (such as a new radio (NR) communication system), or can also be applied to a future communication system, or other similar communication system. Other similar communication systems can include wireless fidelity (WIFI), vehicle to everything (V2X), internet of things (IoT) system, narrow band internet of things (NB-IoT) system, etc.

[0069] The communication method provided by the embodiments of the present application can be applied to a system including a terminal device and a network device. The system can also include a core network device. Any two network devices in the communication system can be connected to the same core network device, or can be connected to different core network devices.

[0070] The communication system can be a 5G NR communication system. The interface between the core network device and the network device is an NG interface, and different network devices are connected through an Xn interface. Taking the network device as a gNB or an ng-eNB and the core network device as an access and mobility management function (AMF) / user plane function (UPF) as an example, the connection relationship between the AMF / UPF and the network device and between different AMF / UPF and network devices can be as shown in FIG. 1.

[0071] In an embodiment of the present application, the network device refers to a radio access network (RAN) device. The RAN can be a 3GPP related cellular system, for example, a 5G / new radio (NR) mobile communication system or a future-oriented evolution system (for example, a 6G mobile communication system). The RAN can also be an open RAN (O-RAN or ORAN), a cloud radio access network (CRAN), or a virtualized RAN (vRAN) and the like. The RAN can also be a communication system in which two or more of the above systems are fused. The RAN device can also be referred to as a RAN node, a RAN entity, or an access node and the like.

[0072] In a possible scenario, the 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 network device in a 6G mobile communication system, a network device in a future mobile communication system, and the like. The RAN node can be a macro network device, a micro network device, an indoor station, a relay node, a donor node / host node, or a wireless controller and the like. The RAN node can also be a server, a wearable device, a vehicle or a vehicle-mounted device and the like. For example, the RAN node in the V2X technology can be a road side unit (RSU).

[0073] In another possible scenario, a RAN node can be a module or unit that completes part of the functions of a network device; or multiple RAN nodes cooperate to assist a terminal device to implement wireless access, and different RAN nodes respectively implement part of the functions of a network device. For example, a RAN node can be a central unit (CU), a distributed unit (DU), or a radio unit (RU), etc. The functions of the CU can be implemented by one entity, or can also be implemented by different entities. For example, the functions of the CU can be further divided, that is, the control plane and the user plane are separated and implemented by different entities, respectively, as a control plane CU entity (that is, a CU-control plane (CP) entity) and a user plane CU entity (that is, a CU-user plane (UP) entity). The CU-CP entity and the CU-UP entity can be coupled with the DU to jointly complete the functions of the RAN node. The CU and the DU can be separately arranged, or can also be included in the same network element, such as a baseband unit (BBU). Any one of the CU (or CU-CP and CU-UP), the DU, and the RU in this application can be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.

[0074] In different systems, the CU (or CU-CP and CU-UP), the DU, or the RU can also have different names, but those skilled in the art can understand their meanings. For example, in an ORAN system, the CU can also be referred to as an O-CU (open CU), the DU can also be referred to as an O-DU, the CU-CP can also be referred to as an O-CU-CP, the CU-UP can also be referred to as an O-CU-UP, and the RU can also be referred to as an O-RU. For the convenience of description, the CU, the CU-CP, the CU-UP, the DU, and the RU are taken as examples for description in this application.

[0075] The CU and the DU can be configured according to protocol layer functions of the wireless network they implement: for example, the CU is configured to implement functions of a packet data convergence protocol (PDCP) layer and protocol layers above the PDCP layer (such as a radio resource control (RRC) layer and / or a service data adaptation protocol (SDAP) layer, etc.); the DU is configured to implement functions of protocol layers below the PDCP layer (such as a radio link control (RLC), a media access control (MAC) layer, and / or a physical (PHY) layer, etc.). For specific descriptions of the above protocol layers, reference can be made to relevant technical specifications of the 3GPP or technical specifications of other applicable communication protocols.

[0076] For example, referring to FIG. 2, two typical protocol stack diagrams of a network device provided in embodiments of the present application are shown. In network device (1), the network device is divided into a CU and a DU, the CU is configured to implement functions of a PDCP layer and protocol layers above the PDCP layer (such as an RRC layer and / or an SDAP layer, etc.); the DU is configured to implement functions of protocol layers below the PDCP layer (such as an RLC layer, a MAC layer, and / or a PHY layer, etc.). The CU and the DU communicate based on an F1 interface. In network device (2), the network device is divided into a CU and a DU, wherein the CU includes a CU-CP and a CU-UP, the CU-CP is used to implement control plane functions of the CU, and the CU-UP is used to implement user plane functions of the CU. The CU-CP and the CU-UP can communicate based on an E1 interface, the CU-CP and the DU communicate based on an F1 interface supporting a control plane (also referred to as F1-C), and the CU-UP and the DU communicate based on an F1 interface for a user plane (also referred to as F1-U). The CU-CP is configured to implement control plane functions of a PDCP layer and RRC layer functions, and the CU-UP is configured to implement user plane functions of the PDCP layer and functions of an SDAP layer. The DU is configured to implement functions of protocol layers below the PDCP layer (such as an RLC layer, a MAC layer, and / or a PHY layer, etc.).

[0077] The above-mentioned processing functions of the CU and the DU are merely examples according to the protocol layer division, and the division can be performed in other manners, which is not limited in the present application. For example, in one design, the CU or the DU can also be divided into partial processing functions with protocol layers. In one design, partial functions of the RLC layer and functions of the protocol layers above the RLC layer are arranged in the CU, and the remaining functions of the RLC layer and functions of the protocol layers below the RLC layer are arranged in the DU.

[0078] In another possible design, the functions of the PHY layer are jointly implemented by the DU and the RU, or described as moving part of the PHY layer functions of the DU to the RU. One DU can be connected with one or more RUs. The functions of the DU and the RU can be configured in multiple manners according to the design. For example, the DU is configured to implement baseband functions, and the RU is configured to implement intermediate frequency functions. For another example, the DU is configured to implement high-layer functions in the PHY layer, and the RU is configured to implement low-layer functions in the PHY layer or implement the low-layer functions and the intermediate frequency functions. The high-layer functions in the PHY layer can include part of the functions of the PHY layer, which are closer to the MAC layer, and the low-layer functions in the PHY layer can include another part of the functions of the PHY layer, which are closer to the intermediate frequency side. The present application does not limit the specific functions of the DU and the RU. The interface between the DU and the RU can be referred to as a front-haul interface. In one design, the CU can have no PDCP layer, for example, the CU only includes the RRC layer. The CU-CP has no PDCP-C. The CU-UP can have no PDCP-U, or have no CU-UP. In one design, the DU can have no RLC layer, for example, the DU only has the MAC and the higher PHY layer.

[0079] When the RAN is an O-RAN, it can also have an artificial intelligence (AI) function, for example, the O-RAN includes an intelligent controller. The intelligent controller can be a non-real time RAN intelligent controller (non-real time RIC / non-RT RIC / NRT RIC), or a near-real time RAN intelligent controller (near-real time RIC / near-RT RIC / nRT RIC). The non-real time RIC can be used to implement non-real time intelligent management of the RAN function, can implement a workflow including model training and model updating, and guide applications / functions in the nRT RIC based on a policy. The near-real time RIC can be used to implement near-real time intelligent management of the RAN. Through data collection and related operations on the E2 interface, near-real time control and optimization of modules and resources of the O-RAN are implemented.

[0080] In the embodiments of the present application, the device for implementing the function of the network device can be the network device itself, or a device capable of supporting the network device to implement the function, such as a chip system or a combination device or component that can implement the function of the network device, which can be installed in the network device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network device.

[0081] In the embodiments of the present application, all devices capable of communicating data with the network device can be regarded as terminal devices. The terminal device is also called a terminal, a terminal device, a user equipment (UE), a user device, a mobile station, or a mobile terminal, etc. The terminal device can be widely applied to various scenes, for example, the terminal device can be a mobile phone, a computer, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a station (STA), a mechanical arm, a camera, a robot, a vehicle, a drone, a helicopter, an airplane, a ship, or a smart home device (such as a television, an air conditioner, a sweeping machine, a sound box, a set-top box), a relay, a customer premise equipment (CPE), etc.

[0082] In addition, in the embodiments of the present application, the terminal device can also be a terminal device in an IoT system, for example, a water meter, an electricity meter, etc. IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network, so as to realize the intelligent network of man-machine interconnection and object-object interconnection.

[0083] Among them, when the terminal device is applied to V2X, it can also be called V2X device, for example, smart car or intelligent car, digital car, unmanned car or driverless car or pilotless car or automobile, self-driving car or autonomous car, pure EV or Battery EV, hybrid electric vehicle (HEV), range extended EV (REEV), plug-in HEV (PHEV), new energy vehicle, RSU.

[0084] As introduced above, various terminal devices can be considered as vehicle-mounted terminal devices if they are located on a vehicle (for example, placed / installed in the vehicle). The vehicle-mounted terminal device can be built-in as one or more components or units in a vehicle-mounted module, a vehicle-mounted module group, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit of the vehicle, and the vehicle can implement the method of the present application through the built-in vehicle-mounted module, vehicle-mounted module group, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit. The vehicle-mounted terminal device can be a whole vehicle device, a vehicle-mounted module, a vehicle, an on board unit (OBU), an RSU, a telematics box (T-box), a chip or a system on chip (SOC), etc. The above chip or SOC can be installed in the vehicle, OBU, RSU or T-box.

[0085] FIG. 3 shows an example diagram of an O-RAN system. It should be understood that the O-RAN system can also include other components than those shown in FIG. 3, which are not specifically limited herein. As shown in FIG. 3, the access network device can communicate with the core network (CN) through a backhaul link, and can communicate with the terminal device through an air interface. For example, the access network device can include a baseband unit (BBU) and a radio unit (RU). The BBU includes at least one CU and at least one DU, and the CU and the DU can communicate through at least one midhaul link. The RU can implement the functions of the lower physical layer (Lower PHY) and the radio frequency (RF). In some examples, the RU can be a 3GPP transmission reception point (TRP) or a remote radio head (RRH) or other similar functional entity. In some examples, the Low-PHY can include part of the PHY processing, such as fast Fourier transform (FFT), inverse fast Fourier transform (IFFT), digital beamforming and filtering, and other processing functions. The BBU can communicate with the CN through a backhaul link, and the RU can communicate with at least one terminal device through an air interface. The BBU can communicate with at least one RU through a front-haul link, and the BBU and the RU can be co-located or not co-located.

[0086] FIG. 4 is a diagram illustrating a network element function split and protocol layer structure of an O-RAN device. It should be noted that the configuration of the CU and the DU shown in FIG. 4 is merely an example, and the CU and the DU can be configured to have functions as needed. For example, the CU or the DU can be configured to have more protocol layer functions, or the CU or the DU can be configured to have partial processing functions of the protocol layer. The DU and the RU can be co-located or not co-located. The DU and the RU can exchange control plane information and user plane information via a lower-layer split-CUS-plane (LLS-CUS) interface through a fronthaul link. The LLS-CUS can include an LLS-C interface and an LLS-U interface that provide a control plane (C-Plane) and a user plane (U-Plane), respectively. In some examples, the control plane (C-Plane) refers to real-time control between the DU and the RU. The DU and the RU have an LLS-M interface of the fronthaul link to exchange management information, and the management plane (M-Plane) refers to non-real-time management operations between the DU and the RU.

[0087] The DU and the RU can cooperate to jointly implement the functions of the PHY layer. One DU can be connected to one or more RUs. The functions of the DU and the RU can be configured in multiple ways according to design. For example, the DU is configured to implement baseband functions, and the RU is configured to implement intermediate radio frequency functions. For another example, the DU is configured to implement high-layer functions in the PHY layer, and the RU is configured to implement low-layer functions in the PHY layer or to implement the low-layer functions and radio frequency functions. The high-layer functions in the PHY layer can include a part of the functions of the PHY layer that are closer to the MAC layer, and the low-layer functions in the PHY layer can include another part of the functions of the PHY layer that are closer to the intermediate radio frequency side.

[0088] In the embodiments of the present application, the device for implementing the function of the terminal device can be the terminal device itself, or a device capable of supporting the terminal device to implement the function, such as a chip system or a combination device or component that can implement the function of the terminal device, which can be installed in the terminal device. The embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.

[0089] Taking a network device as a network device and a terminal device as a UE as an example, the network device and the UE can be fixed in position or movable. The network device and the UE can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; can also be deployed on the water surface; and can also be deployed on an airplane, a balloon, and a man-made satellite. The embodiments of the present application do not limit the application scenarios of the network device and the UE.

[0090] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0091] The technical features related to the embodiments of the present application are introduced below.

[0092] As shown in FIG. 5, it is a flowchart of a communication method provided by the embodiments of the present application. FIG. 5 introduces the method from the perspective of the interaction between the network device and the terminal device. It should be understood that the method can also be implemented by other apparatuses, for example, by a chip or a communication apparatus with a communication function. The chip and the communication apparatus can be arranged in the network device and the terminal device, or can be used in combination with the network device and the terminal device. When the execution subject is other apparatuses, the receiving / sending can be understood as input / output, that is, the apparatus communicates with other modules or components of the terminal and the network device, or communicates with the terminal device and the network device. In addition, the processing performed by a single execution subject can also be divided into processing performed by multiple execution subjects, which can be logically and / or physically separated. For example, the processing performed by the network device can be divided into processing performed by at least one of the CU, the DU, the RU, and the like.

[0093] The method comprises:

[0094] S501, the terminal device displays an icon corresponding to the first experience level.

[0095] In the present application, different experience levels are mapped to different communication configurations. The experience level can be device level, user level, or service level. Taking the device level as an example, the first experience level is the experience level of the terminal device. The device level experience level can also be referred to as the device experience level. Taking the user level as an example, the first experience level is the experience level of the user using the terminal device. The user level experience level can also be referred to as the user experience level. Taking the service level as an example, the first experience level is the experience level of the service running on the terminal device. The service level experience level can also be referred to as the service experience level.

[0096] The communication configuration can include at least one of the following: slice resource, QoS configuration, QoE configuration, subnet resource, and resource scheduling strategy. The experience level can be one or more of the following: slice level, QoS guarantee level, QoE guarantee level, subnet level, and resource scheduling level. The above configurations are introduced below.

[0097] 1. Slice resource

[0098] The standardized experience levels (also referred to as slice levels) can be defined in the standard, and different experience levels are associated with different slice resources, where the slice resources can be indicated by slice resource information (also referred to as slice information or slice resource guarantee information), which can also be described as different experience levels being associated with different slice resource information. Specifically, the slice resources can include one or more of slice access network resources, slice core network resources, and slice transport network resources. The slice access network resources can also be referred to as slice resources of the access network, the slice core network resources can also be referred to as slice resources of the core network, and the slice transport network resources can also be referred to as slice resources of the transport network. It should be noted that the naming of the slices is not limited in the present application.

[0099] The slice resources of the access network can include at least one of the following: a number of dedicated resource blocks (RBs) (also referred to as a dedicated RB guarantee number or a dedicated RB guarantee value), low-frequency carrier priority enablement (also referred to as low-frequency carrier priority or low-frequency priority enablement or low-frequency priority), carrier exclusivity enablement (also referred to as dedicated carrier or exclusive carrier), time domain scheduling priority enablement (also referred to as time domain scheduling priority or time domain priority enablement), and resource guarantees in multiple aspects.

[0100] The slice resources of the core network can include at least one of the following: a virtual network function (VNF) network element that is exclusively occupied (for example, an AMF, a UPF, a session management function (SMF), a unified data management (UDM), a policy control function (PCF), etc.), a VNF network element that is partially shared by multiple slices (for example, one or more of an AMF, a UPF, an SMF, a UDM, and a PCF that are partially shared by multiple slices), and a VNF network element that is shared by all slices (for example, an AMF, a UPF, an SMF, a UDM, and a PCF that are shared by all slices).

[0101] The slice resources of the transport network can include at least one of the following: transport resources of the transport network, segment routing transport profile (SR-TP) tunnels, SR-TP operation administration and maintenance (OAM) detection techniques, and rerouting protection.

[0102] The terminal device obtains the end-to-end experience level information (also referred to as slice level information) from the operator network after signing a contract with the operator or through certain interaction between the terminal device and the operator network, which can include slice level and / or slice resource information, and the specific acquisition process will be introduced below. Optionally, the terminal device interface can display the icon (Logo) corresponding to the differentiated experience level, and the differentiated experience level can be associated with different slice resources defined by the standard. The specific display of the Logo is customized by the operator. For example, the corresponding relationship between the slice resource information and the slice level can be as shown in Table 1.

[0103] Table 1

[0104] It should be noted that in addition to the slice resources listed in Table 1, other slice resources can also be further included, and the present application does not limit this. For example, taking the slice resources of the access network as an example, the network can also provide more fine-grained slice resources, such as SR resources for sending scheduling requests (SR), random access resources for access, and the like.

[0105] 2. QoS configuration

[0106] The standardized experience level (also referred to as QoS guarantee level) can be defined in the standard, and different experience levels are associated with different QoS configurations, wherein the QoS configuration can be indicated by QoS information (also referred to as QoS guarantee information), and this method can also be described as different experience levels being associated with different QoS information. Specifically, the QoS configuration can include at least one of the following: QoS identifier (such as QoS class identifier (QCI), 5G QoS identifier (5QI)), allocation and retention priority (ARP), guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), average maximum flow bit rate (AMBR), reflective QoS attribute (RQA), notification control, and maximum packet loss rate.

[0107] The terminal device obtains experience level information (may also be referred to as QoS level information or QoS guarantee level information) from the operator network after signing a contract with the operator or through message interaction between the terminal device and the operator network, which can include QoS guarantee level and / or QoS information. The specific acquisition process will be described below. Optionally, the icon (Logo) corresponding to the differentiated experience level can be displayed on the terminal device interface. The differentiated experience level can be associated with different QoS configurations defined by the standard. The specific display of which logo is customized by the operator. Exemplarily, the corresponding relationship between QoS information and experience level can be as shown in Table 2.

[0108] Table 2

[0109] It should be noted that in the above Table 2, the QoS guarantee identifier can be QCI or 5QI, or other identifiers representing QoS defined in future systems.

[0110] 3. QoE configuration

[0111] The standardized experience level (may also be referred to as QoE guarantee level) can be defined in the standard. Different experience levels are associated with different QoE configurations, wherein the QoE configuration can be indicated by QoE information (may also be referred to as QoE guarantee information). This approach can also be described as different experience levels being associated with different QoE information. Specifically, the QOE configuration can include at least one of the following: uplink guaranteed delay, downlink guaranteed delay, uplink guaranteed rate, downlink guaranteed rate, reliability guarantee, packet loss rate guarantee, guaranteed jitter, task success rate, service success rate, guaranteed code rate, definition, frame rate, resolution, operation response time, call setup delay, handover response delay, and two-way end-to-end delay.

[0112] The terminal device obtains experience level information (may also be referred to as QoE level information or QoE guarantee level information) from the operator network after signing a contract with the operator or through message interaction between the terminal device and the operator network, which can include QoE guarantee level and / or QoE information. The specific acquisition process will be described below. Optionally, the icon (Logo) corresponding to the differentiated experience level can be displayed on the terminal device interface. The differentiated experience level can be associated with different QoE configurations defined by the standard. The specific display of which logo is customized by the operator. Exemplarily, the corresponding relationship between QoS information and experience level can be as shown in Table 2.

[0113] Table 3

[0114] It should be noted that the values in Table 3 above are only specific examples of some QoE parameters, and in actual standard formulation, different parameters can be selected and values can be determined according to different service conditions or different industry conditions.

[0115] 4. Subnet resources

[0116] In future communication systems, a subnet can be introduced. The subnet is mainly for a home environment, a concert hall, a shopping mall, an office park, a campus, an amusement park, a museum, and other consumer-oriented life, entertainment, office park, and other areas.

[0117] Based on different needs of customers, the subnet can provide customized service capabilities, such as providing multicast services to a concert hall, providing computing power services in an office park, and providing mobile application augmented reality (AR) / virtual reality (VR) immersive large-bandwidth low-latency services to homes, amusement parks, and museums, etc. These customized service capabilities generally only need to be provided within a certain area range, and do not need to be spread in a wide area. The "regional" feature and customized service capability are exactly matched with the characteristics of high frequency, low penetration, large capacity, large bandwidth, and low latency of millimeter wave, terahertz, etc., and are easy to form a subnet to provide services for users.

[0118] The subnet shares the basic wireless and network resources of the large network, the subnet is fully isolated from the large network, and the subnet can share services for multi-operator users. In addition, a terminal device can be connected to the large network and the subnet at the same time, realizing multiple identities without changing cards, numbers, and terminals, and the application of the terminal device can perceive the subnet and access the customized services in the subnet as needed. If the services of the subnet are not needed, the terminal device can only stay on the basic connection of the large network or the basic connection of the subnet.

[0119] In addition, the subnet has a high dynamic feature. The subnet can be temporary for a few hours or for a longer period of time, which can well support "one-time" activities such as carnivals and concerts.

[0120] At the same time, from the perspective of operators, according to people's activities, such as going to work or school during the day, going to concerts and sports matches at night on weekends, and going to amusement parks and museums during the winter and summer vacations, the subnet can be dynamically turned on and off and scaled to improve the utilization rate of resources.

[0121] The customized service capabilities of the subnet can provide large-bandwidth low-latency capabilities for designated areas with the help of millimeter wave base stations, and can also be combined with positioning, sensing, multicast, edge computing, and computing power capabilities.

[0122] Therefore, compared to the private network model of previous 5G systems, subnets can overcome pain points such as high purchase costs, long deployment times, lack of support for sharing users from multiple operators, and insufficient operational openness. Subnets have significant advantages such as the ability to provide superior service, flexible deployment, and network autonomy.

[0123] Introducing subnets into future communication systems allows for differentiated user experiences through differentiated subnet services. Similar to the three configurations mentioned earlier, standardized experience levels (also known as subnet levels or subnet types) can be defined in the standard. Different experience levels are associated with different subnet resources, which can be indicated by subnet information (also known as subnet guarantee information). This approach can also be described as different experience levels being associated with different subnet information.

[0124] Specifically, subnet information may include, but is not limited to, one or more of the following: subnet resources, such as subnet access network resources (also known as access network subnet resources), subnet core network resources (also known as core network subnet resources), and subnet transmission network resources (also known as transmission network subnet resources), and subnet configuration. It should be noted that this application does not limit the naming of the aforementioned subnets.

[0125] After signing a contract with an operator, or through message exchange with the operator's network, the terminal device obtains experience level information (also known as subnet level information or subnet type information). This information may include subnet level (or subnet type) and / or subnet information. For example, it may establish a subnet connection with the operator's network to obtain subnet information and determine the subnet level (or subnet type) corresponding to the established subnet. Optionally, an icon (Logo) corresponding to the "Differentiated Experience Level" may be displayed on the terminal device interface. The differentiated experience level is associated with different subnet types, different subnet levels, or subnet information defined by the standard. The specific logo displayed is determined by the operator.

[0126] 5. Resource scheduling strategy

[0127] Resource scheduling strategies can include at least one of the following: prioritizing the allocation of a large number of RB resources within a scheduling time unit; allocating at least M RB resources within a scheduling time unit; prioritizing the use of low-order modulation and coding formats within a scheduling time unit; and using modulation and coding formats no higher than X within a scheduling time unit, where M is a positive integer and X is a predefined modulation and coding format or a network-configured modulation and coding format threshold. These resource scheduling strategies can save power consumption during terminal device communication, improve the battery life of high-level users' terminal devices, and provide a better user experience.

[0128] Resource scheduling strategies can also include selecting one or more of the following configurations for users or terminals with different experience levels: the number of multiple-input multiple-output (MIMO) layers, the number of transmit / receive antennas, the number of carriers, or the carrier bandwidth. For example, if the experience level prioritizes reducing the heat generation of the terminal device, then fewer MIMO layers, fewer antennas, fewer carriers, or a smaller carrier transmission bandwidth can be prioritized. If the experience level prioritizes high-speed transmission, then more MIMO layers, more transmit / receive antennas, more carriers, or a larger carrier transmission bandwidth can be configured.

[0129] In this application, the resource scheduling strategy may also be referred to as wireless resource scheduling strategy, wireless RB scheduling strategy, RB scheduling strategy, etc.

[0130] After signing a contract with an operator, or through message exchange between the terminal device and the operator's network, the terminal device obtains experience level information (also known as resource scheduling policy information or resource scheduling policy guarantee information) from the operator's network. This information may include resource scheduling level and / or resource scheduling information. The specific acquisition process will be described below. Optionally, an icon (Logo) corresponding to the "differentiated experience level" can be displayed on the terminal device interface. The differentiated experience level can be associated with different resource scheduling policies defined by the standard. The specific Logo displayed is determined by the operator.

[0131] This application predefines multiple experience levels, each mapping to different communication configurations. Terminal devices can display icons corresponding to these experience levels, allowing users to experience differentiated communication in real time and enhancing their sense of accessibility to these differentiated experiences. Furthermore, standardizing experience levels increases the credibility of the user experience, thereby further enhancing the overall user experience.

[0132] Before displaying the icon corresponding to the first experience level, the terminal device can determine that the access network device or core network device supports or enables the first service. Alternatively, if the experience level is device-level, it can determine that the access network device or core network device enables the first service for the terminal device; if the experience level is user-level, it can determine that the access network device or core network device enables the first service for the user using the terminal device; and if the experience level is service-level, it can determine that the access network device or core network device enables the first service for the service running on the terminal device. For example, before displaying the icon corresponding to the first experience level, the terminal device can receive a first message indicating that the access network device or core network device supports or enables the first service, or indicating that the access network device or core network device enables the first service for the terminal device, the user using the terminal device, or the service running on the terminal device. The first service refers to configuring the corresponding communication configuration for the experience level. The first message can originate from the access network device or the core network device. It should be noted that the messages and information in this application can originate from the same device or different devices.

[0133] For example, the first message could be system information, a connection release message, or other non-access stratum (NAS) messages.

[0134] It should be understood that "First Service" is merely an exemplary name. In specific implementations, "First Service" can also be called differentiated service, differentiated experience service, differentiated communication, differentiated experience, etc.

[0135] Before displaying the icon corresponding to the first experience level, the terminal device can also determine that the current experience level is the first experience level. For example, the terminal device can receive a second message carrying experience level information. This second message can come from either the access network device or the core network device. For example, the second message could be a Nudm_UECM_Regitration response message, a Nudm_SDM_Get_Response message, a PDU session establishment message, a PDU session reconstruction message, a registration acceptance message, a configuration update message, etc.

[0136] For example, taking slice resources as an example, if a terminal device signs up for a slice package with an operator, the operator can send the slice level information and / or logo of the slice package to the terminal device. This process can be achieved through network elements (such as UDM or PCF) of the local public land mobile network / home public land mobile network (HPLMN), AMF (in roaming scenarios, it is the visited public land mobile network (VPLMN) AMF; in non-roaming scenarios, it is the HPLMN AMF), and other devices.

[0137] Depending on whether AMF is aware of slice-level information, there are two possible solutions.

[0138] Option 1: The AMF senses slice level information. The process by which the terminal device obtains slice level information may include: the AMF obtaining slice level information from the UDM, for example, through the Nudm_UECM_Regitration response message or the Nudm_SDM_Get_Response message. If, during the registration process, the AMF obtains changed slice level information from the HPLMN UDM / PCF, the AMF can send it to the terminal device through a registration acceptance message or a configuration update message.

[0139] The slice level information is sent to the terminal device through registration acceptance messages or configuration update messages, and the AMF can perceive the slice level information.

[0140] Option 2: The AMF is unaware of slice level information. The process by which the terminal device obtains slice level information can include: the AMF obtaining slice level information from the UDM, for example, through the Nudm_UECM_Regitration response message or the Nudm_SDM_Get_Response message. The AMF can send the slice level information to the terminal device in the form of a container, for example, by carrying a container in the DL NAS transport message, which carries the slice level information. The contents of the container can have security mechanisms, such as integrity protection, to prevent the AMF (such as a roaming PLMN) from tampering with it.

[0141] Taking QoS configuration as an example, if the terminal device signs a QoS guarantee agreement with the operator, the operator can send QoS level information to the UE, and there may be the following three solutions.

[0142] Option 3: The AMF obtains QoS level information from the UDM, for example, through the Nudm_UECM_Regitration response message or the Nudm_SDM_Get_Response message. If the AMF obtains changed QoS level information from the HPLMN UDM / PCF during the terminal device registration process, the AMF can send it to the terminal device through a registration acceptance message or a configuration update message.

[0143] Option 4: The AMF obtains QoS level information from the UDM, for example, through the Nudm_UECM_Regitration response message or the Nudm_SDM_Get_Response message. The AMF can distribute the QoS guarantee level to the terminal device in the form of a container, for example, by carrying a container containing QoS level information in the DL NAS transport message. The contents of the container can have security mechanisms, such as integrity protection, to prevent tampering by the AMF (e.g., a roaming PLMN).

[0144] Option 5: The SMF can sense the QoS level information of the terminal device, so it can send QoS level information to the terminal device during the establishment or modification of the PDU session. If the QoS flow established by the PDU session is service-level, the SMF can send service-level QoS level information to the terminal device.

[0145] Taking QoE configuration as an example, if the terminal device signs a QoE protection agreement with the operator, the operator can send QoE level information to the UE.

[0146] In one alternative approach, a method similar to QoS configuration can be used, as detailed in Schemes 3 to 5 above, which will not be elaborated upon here.

[0147] In another alternative approach, the network can also distribute the mapping relationship between QoE protection level and QoE information. The terminal device calculates the current QoE protection level through QoE information (such as uplink protection latency). The possible ways to distribute this mapping table are as follows: The AMF can distribute the information indicating the mapping relationship between QoE protection level and QoE information to the terminal device through registration acceptance messages or configuration update messages.

[0148] In one possible implementation, before displaying the icon corresponding to the first experience level, the terminal device may further determine that the communication configuration configured by the network device satisfies the communication configuration corresponding to the first experience level. For example, before displaying the icon corresponding to the first experience level, the terminal device may receive first information, which indicates the communication configuration configured for the terminal device, wherein the communication configuration indicated by the first information satisfies the communication configuration corresponding to the first experience level. The first information may come from the access network device or the core network device.

[0149] For example, the first information can be the communication configuration in the second message. For instance, if the experience level is a slice level, the first information can be slice resource information in the second message. If the experience level is a QoS guarantee level, the first information can be QoS information in the second message. If the experience level is a QoS guarantee level, the first information can be QoE information in the second message. If the experience level is a subnet level, the first information can be subnet information.

[0150] As an optional approach, the terminal device can also request additions or modifications (e.g., increases or decreases) to the experience level / communication configuration. For example, the terminal device can send a third message: if the experience level is device-level, the third message requests additions or modifications (e.g., increases) to the terminal device's experience level / communication configuration. If the experience level is user-level, the third message requests additions or modifications (e.g., increases) to the experience level / communication configuration of users using the terminal device. If the experience level is service-level, the third message requests additions or modifications (e.g., increases) to the experience level / communication configuration of the first service running on the terminal device. Taking an increase as an example, after increasing the experience level / communication configuration, the terminal device can display an icon indicating the increased experience level. The third message can originate from either the access network device or the core network device.

[0151] For example, if the experience level is a slice level, the third message can be a slice service establishment request or a slice establishment request. If the experience level is a QoS guarantee level, QoE guarantee level, subnet level, resource scheduling level, etc., the third message can be a QoS flow establishment request, a PDU session establishment request, etc.

[0152] Optionally, before requesting the addition or modification (e.g., improvement) of the experience level / communication configuration, the terminal device may display a first prompt, asking the user whether to add or modify (e.g., improve) the experience level. Specifically, if the experience level is device-level, the first prompt asks the user whether to add or modify (e.g., improve) the terminal device's experience level / communication configuration. If the experience level is user-level, the first prompt asks the user whether to add or modify (e.g., improve) the experience level / communication configuration of the user using the terminal device. If the experience level is service-level, the first prompt asks the user whether to add or modify (e.g., improve) the experience level / communication configuration of the first service running on the terminal device. Based on this approach, the terminal device may respond to the user's first operation by sending a third message, the first operation being used to confirm the addition or modification (e.g., improvement) of the experience level / configuration information.

[0153] The aforementioned first prompt can be displayed by the terminal device when it determines that an increase or modification (e.g., an improvement) in the experience level is needed, or it can be displayed when triggered by a fourth message from the network. Assuming the modification to the experience level is an improvement, taking the experience level as a service level as an example, if the terminal device determines that the service quality of the first service does not meet the user's requirements, or that the service quality of the first service is less than or equal to a threshold value, it can display the first prompt, which asks the user whether to improve the experience level / communication configuration of the first service running on the terminal device. Alternatively, if the terminal device receives a fourth message indicating that the experience level of the first service running on the terminal device is low (or needs to be improved), it can display the first prompt, which asks the user whether to improve the experience level / communication configuration of the first service running on the terminal device.

[0154] The fourth message can be sent by the network side when it determines that the service quality of the first service does not meet the user's requirements, or when the service quality of the first service is less than or equal to a threshold value. The fourth message can originate from either the access network equipment or the core network equipment.

[0155] For example, if the experience level is a slice level, the fourth message can be a slice service establishment message or a slice establishment message. If the experience level is a QoS guarantee level, QoE guarantee level, subnet level, resource scheduling level, etc., the fourth message can be a QoS flow establishment message, a PDU session establishment message, etc.

[0156] Optionally, the terminal device may also obtain information about the first service. This information includes communication configurations corresponding to N experience levels, where N is a positive integer, and the first experience level is one of the N experience levels. The information about the first service may be pre-configured, or it may come from the access network device or the core network device.

[0157] The following example illustrates the differentiated display using the communication configuration described above.

[0158] Example 1: Communication is configured as a slice resource. For ease of understanding, the first service in Example 1 will be referred to as the Differentiated Slice Service.

[0159] Taking user-level experience level or device-level experience level as an example, in idle state, the terminal device determines the display of differentiated experience icons through either of the following two methods.

[0160] Method 1: The user or terminal device signs up for a differentiated slicing service with the operator. The terminal device obtains the corresponding slicing level information through the second message and displays the corresponding level icon on the terminal device's display interface.

[0161] Method 2: The terminal device determines whether the current network enables differentiated slicing services by receiving the first message sent by the network (such as system information, connection release messages, or other non-access stratum (NAS) messages), or whether the current network is for the user using the terminal device / that the terminal device has differentiated slicing services enabled. If the terminal device determines that differentiated slicing services are enabled, it displays the corresponding level icon. Specifically, the terminal device's access layer may instruct higher layers to display the corresponding level icon, or the terminal device's NAS layer may instruct higher layers to display the corresponding level icon.

[0162] Taking user-level or device-level experience levels as examples, in connected mode, the terminal device receives network-configured slice resource information. If, based on this information, the network-issued resource configuration meets the user's subscribed slice level, the terminal device displays the corresponding level's icon. Specifically, if the slice resource information is received by the access layer, the access layer notifies the upper layer to display the corresponding level's icon. If the slice resource information is received by the NAS layer, the NAS layer notifies the upper layer to display the corresponding level's icon.

[0163] Taking the service-level experience level as an example, if the experience guarantee is based on the service, it does not strictly require users to sign a contract with the operator in advance to enable the differentiated slicing service. The terminal device can quickly enable or customize the differentiated slicing service based on temporary service needs to improve the user experience for that specific service.

[0164] The process by which a terminal device determines the display of differentiated experience icons may include:

[0165] A1. The terminal device obtains relevant information about differentiated slicing services from the network or preset configuration, such as slicing resource information corresponding to different slicing levels or different slicing resource configurations.

[0166] A2. When a certain service (such as a game or video conferencing) is started or during the course of a certain service, the terminal device can proactively, for example, based on the terminal device's assessment of the service quality, initiate a differentiated slice request when the service quality does not meet the user's requirements or falls below a certain threshold. This request sends a request to the network to establish a new slice service (such as a differentiated slice service), triggering the terminal device to establish a temporary differentiated slice service with the network to improve the service experience quality.

[0167] Alternatively, the terminal device can also be passive, for example, by sending a request to the network to establish a new slice service (such as a differentiated slice service) under the prompt of a pop-up selection window on the terminal device interface, such as a slice establishment request, to trigger the establishment of a temporary differentiated slice service with the network to improve the quality of service experience.

[0168] A3: The network allocates end-to-end slice resources to terminal devices and establishes differentiated slices for terminal devices.

[0169] A4. Based on the slice level information provided by the network, the terminal device notifies the upper layer to display the corresponding icon on the terminal device interface.

[0170] Example 2: Communication is configured for QoS. For ease of understanding, the first service in Example 2 will be referred to as the differentiated QoS service.

[0171] Taking user-level experience level or device-level experience level as an example, in idle state, the terminal device determines the display of differentiated experience icons through either of the following two methods.

[0172] Method 1: Users or terminal devices sign up for differentiated QoS services with operators, and the terminal devices obtain the corresponding QoS level information and display the corresponding level icon on the terminal device display interface.

[0173] Method 2: The terminal device determines whether the current network enables differentiated QoS services by receiving the first message sent by the network (such as system information, connection release messages, or other non-access stratum (NAS) messages), or whether the current network is for the user using the terminal device / that the terminal device has differentiated QoS services enabled. If the terminal device determines that differentiated QoS services are enabled, it displays the corresponding level icon. Specifically, the terminal device's access layer may instruct higher layers to display the corresponding level icon, or the terminal device's NAS layer may instruct higher layers to display the corresponding level icon.

[0174] Taking user-level or device-level experience levels as examples, in connected mode, the terminal device receives QoS information configured by the network. If, based on the QoS guarantee information, the network-issued resource configuration meets the user's subscribed QoS guarantee level, the terminal device displays the corresponding level's icon. Specifically, if the slice configuration information is received by the access layer, the access layer notifies the upper layer to display the corresponding level's icon. If the QoS level information is received by the NAS layer, the NAS layer notifies the upper layer to display the corresponding level's icon.

[0175] Taking the service-level experience level as an example, if the experience guarantee is based on the service, it does not strictly require users to sign a contract with the operator in advance to enable the differentiated QoS service. The terminal device can quickly enable or customize the differentiated QoS service based on the temporary service needs to improve the user experience for the specific service.

[0176] The process by which a terminal device determines the display of differentiated experience icons may include:

[0177] B1. The terminal device obtains relevant information about differentiated QoS services from the network or preset configuration, such as QoS level information corresponding to different QoS levels.

[0178] B2. When a service (such as gaming or video conferencing) is started or during the course of a service, the terminal device can proactively, for example, based on its assessment of the service quality, initiate a differentiated QoS request when the service quality does not meet user requirements or falls below a certain threshold. This request sends a request to the network to establish a new QoS service (such as a differentiated QoS service). For example, this could be a QoS flow establishment request to establish a new QoS flow, a new protocol data unit (PDU) session, or a PDU session establishment request to modify the QoS configuration of a current QoS or PDU session. This triggers the terminal device to establish a temporary differentiated QoS service with the network to improve the service experience quality.

[0179] Alternatively, the terminal device can also be passive, for example, by sending a request to the network to establish a new QoS service (such as a differentiated QoS service) in response to a pop-up prompt on the terminal device interface, thereby triggering the establishment of a temporary differentiated QoS service with the network to improve the quality of service experience.

[0180] B3. The network assigns new QoS configurations to terminal devices, establishing differentiated QoS services for them. This could be a QoS flow establishment message to create a new QoS flow, a new PDU session, or a PDU session establishment message to modify the QoS configuration of a current QoS or PDU session.

[0181] B4. The terminal device notifies the upper layer to display the corresponding icon on the terminal device interface based on the experience level corresponding to the QoS service level information provided by the network.

[0182] Example 3: Communication is configured for QoE. For ease of understanding, the first service in Example 3 will be referred to as the Differentiated QoE Service.

[0183] Taking user-level experience level or device-level experience level as an example, in idle state, the terminal device determines the display of differentiated experience icons through either of the following two methods.

[0184] Method 1: Users or terminal devices sign up for differentiated QoE services with operators, and the terminal devices obtain the corresponding QoE level information and display the corresponding level icon on the terminal device display interface.

[0185] Method 2: The terminal device determines whether the current network enables differentiated QoE service by receiving the first message sent by the network (such as system information, connection release message, or other non-access stratum (NAS) messages), or whether the current network is for the user using the terminal device / that the terminal device has differentiated QoE service enabled. If the terminal device determines that differentiated QoE service is enabled, it displays the corresponding level icon. Specifically, the terminal device's access layer may instruct higher layers to display the corresponding level icon, or the terminal device's NAS layer may instruct higher layers to display the corresponding level icon.

[0186] Taking user-level or device-level experience levels as examples, in connected mode, the terminal device receives the network configuration QoE information. If, based on the QoE information, the network-issued resource configuration meets the user's subscribed QoE level, the terminal device displays the corresponding level's icon. Specifically, if the QoE level information is received by the access layer, the access layer notifies the upper layer to display the corresponding level's icon. If the slice configuration information is received by the NAS layer, the NAS layer notifies the upper layer to display the corresponding level's icon.

[0187] Taking the service-level experience level as an example, if the experience guarantee is based on the service, it does not strictly require users to sign a contract with the operator in advance to enable the differentiated QoE service. The terminal device can quickly enable or customize the differentiated QoE service based on temporary service needs to improve the user experience for that specific service.

[0188] The process by which a terminal device determines the display of differentiated experience icons may include:

[0189] C1, the terminal device obtains relevant information about differentiated QoE services from the network or preset configuration, such as QoE level information corresponding to different QoE levels.

[0190] C2. When a service (such as gaming or video conferencing) is started or during the course of a service, the terminal device can proactively, for example, based on its assessment of the service quality, initiate a differentiated service establishment request when the service quality does not meet user requirements or falls below a certain threshold. This request sends a request to the network to establish a new service flow (such as a differentiated QoE service) (e.g., a QoS flow establishment request or a PDU establishment request), triggering the terminal device to establish a temporary differentiated QoE service with the network to improve the service experience quality.

[0191] Alternatively, the terminal device can also be passive, for example, by sending a request to the network to establish a new service flow (such as a differentiated QoE service) (such as a QoS flow establishment request or PDU establishment request) under the prompt of a pop-up selection window on the terminal device interface, thereby triggering the establishment of a temporary differentiated service with the network to improve the quality of service experience.

[0192] C3: The network allocates new QoE configurations to terminal devices to establish differentiated experience services for them. This could be by establishing new service flows or PDU sessions, or by modifying the QoE guarantee configuration of a current service flow or PDU session.

[0193] C4: Based on the experience level information of the QoE service guarantee provided by the network, the terminal device notifies the upper layer to display the corresponding icon on the terminal device interface.

[0194] Example 4: Communication is configured as a subnet resource. For ease of understanding, the first service will be referred to as the Differentiated Subnet Service in Example 4.

[0195] Taking user-level experience level or device-level experience level as an example, the terminal device determines the display of differentiated experience icons through either of the following two methods.

[0196] Method 1: Users or terminal devices sign up for differentiated subnet services with operators or register to a certain subnet. The terminal devices obtain the corresponding subnet level information and display the corresponding level icon on the terminal device display interface.

[0197] Method 2: The terminal device determines whether the differentiated subnet service is enabled on the current network, or whether the current network is for the user using the terminal device / the terminal device has differentiated subnet service enabled, by receiving the first message sent by the network (such as system information, connection release message, or other non-access stratum (NAS) messages). If the terminal device determines that differentiated subnet service is enabled, it displays the corresponding level icon. Specifically, the terminal device's access layer may instruct higher layers to display the corresponding level icon, or the terminal device's NAS layer may instruct higher layers to display the corresponding level icon.

[0198] Taking user-level or device-level experience levels as examples, in connected mode, the terminal device receives subnet information configured by the network and displays the corresponding level icon. Specifically, if the subnet level information is received by the access layer, the access layer notifies the upper layer to display the corresponding level icon. If the subnet configuration information is received by the NAS layer, the NAS layer notifies the upper layer to display the corresponding level icon.

[0199] Taking the service-level experience level as an example, if the experience guarantee is based on the service, it does not strictly require users to sign a contract with the operator in advance to enable the differentiated subnet service. The terminal device can quickly enable or customize the differentiated subnet service based on temporary service needs to improve the user experience for that specific service.

[0200] The process by which a terminal device determines the display of differentiated experience icons may include:

[0201] D1. The terminal device obtains relevant information about differentiated subnet services from the network or preset configuration, such as subnet level information corresponding to different subnet levels.

[0202] D2. When a service (such as gaming or video conferencing) is started or during the course of a service, the terminal device can proactively, for example, based on its assessment of the service quality, initiate a differentiated service establishment request when the service quality does not meet user requirements or falls below a certain threshold. This request sends a request to the network to establish a new service flow (such as a differentiated subnet service) (e.g., a QoS flow establishment request or a PEU session establishment request), triggering the terminal device to establish a temporary differentiated subnet service with the network to improve the service experience quality.

[0203] Alternatively, the terminal device can passively send a request to the network to establish a new service flow (such as a differentiated subnet service) (e.g., a QoS flow establishment request or a PEU session establishment request) in response to a pop-up prompt on the terminal device interface, thereby triggering the establishment of a temporary differentiated service with the network to improve the quality of service experience.

[0204] D3: The network allocates a new subnet configuration to the terminal device to establish differentiated experience services for the terminal device. For example, it may establish a new service flow, PDU session, or modify the subnet configuration of a current service flow or PDU session.

[0205] D4. Based on the experience level information of the subnet service guarantee provided by the network, the terminal device notifies the upper layer to display the corresponding icon on the terminal device interface.

[0206] When communication is configured with a resource scheduling strategy, the way the terminal device determines the display of differentiated experience icons is similar to that in Examples 1 to 4 above, and will not be explained further here.

[0207] Based on the same inventive concept as the method embodiment, this application provides a communication device. The structure of the communication device can be as shown in FIG6, including a processing unit 602 and a communication unit 601.

[0208] In one embodiment, the communication device can specifically be used to implement the method executed by the terminal device in the embodiment of FIG5. The device can be the terminal device itself, or a chip or chipset within the terminal device, or a part of the chip used to execute the relevant method function. The processing unit 602 is used to display an icon corresponding to a first experience level, where the first experience level is the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of a first service running on the terminal device; wherein different experience levels are mapped to different communication configurations.

[0209] Optionally, the communication unit 601 is configured to receive a first message, the first message being used to indicate that the access network device or core network device supports or enables a first service, or the first message indicating that the access network device or core network device enables the first service for the terminal device or the user using the terminal device or the first service running on the terminal device; wherein, the first service is a communication configuration configured according to the experience level.

[0210] Optionally, the communication unit 601 is configured to receive first information, the first information being configured to indicate a communication configuration for the terminal device, wherein the communication configuration indicated by the first information satisfies the communication configuration corresponding to the first experience level.

[0211] Optionally, the communication unit 601 is configured to receive a second message, the second message carrying experience level information, the experience level information indicating the first experience level.

[0212] Optionally, the communication unit 601 is used to send a third message, the third message being used to request the addition or modification of the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the first service running on the terminal device.

[0213] Optionally, the processing unit 602 is further configured to display a first prompt, which is used to ask the user whether to add or modify the experience level of the terminal device or the experience level of the user using the terminal device or the experience level of the first service running on the terminal device.

[0214] Optionally, when sending the third message, the communication unit 601 is specifically used to respond to the user's first operation and send the third message, wherein the first operation is used to confirm the addition or modification of the experience level of the terminal device or the experience level of the user using the terminal device or the experience level of the first service running on the terminal device.

[0215] Optionally, the processing unit 602 is further configured to determine that the service quality of the terminal device or the first service does not meet the user requirements, or that the service quality of the terminal device or the first service is less than or equal to a threshold value.

[0216] Optionally, the communication unit 601 is configured to receive a fourth message, the fourth message being used to indicate the addition or modification of the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the first service running on the terminal device.

[0217] Optionally, the communication unit 601 is used to obtain information about a first service, the information of which includes communication configurations corresponding to N experience levels, where N is an integer greater than 0, and the first experience level is one of the N experience levels; wherein, the first service is configured with corresponding communication configurations for experience levels, the information of the first service is pre-configured, or the information of the first service comes from an access network device or a core network device.

[0218] In one embodiment, the communication device can specifically be used to implement the method executed by the network device in the embodiment of FIG5. The device can be the network device itself, or a chip or chipset within the network device, or a part of a chip used to execute the relevant method function. Specifically, the processing unit 602 is used to send a second message or first information through the communication unit 601. The second message carries experience level information, which indicates the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the service running on the terminal device. The first information is used to indicate the communication configuration configured for the terminal device, wherein the communication configuration indicated by the first information satisfies the communication configuration corresponding to the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the service running on the terminal device.

[0219] Optionally, the processing unit 602 is further configured to send a first message through the communication unit 601, the first message being used to indicate that the access network device or core network device supports or enables a first service, or the first message indicating that the access network device or core network device enables the first service for the terminal device or the user using the terminal device or the service running on the terminal device; wherein, the first service is a communication configuration configured according to the experience level.

[0220] Optionally, the processing unit 602 is further configured to send information about a first service through the communication unit 601. The information about the first service includes communication configurations corresponding to N experience levels, where N is an integer greater than 0. The experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the service running on the terminal device is one of the N experience levels. The first service is configured with corresponding communication configurations for the experience levels.

[0221] Optionally, the processing unit 602 is further configured to receive a third message through the communication unit 601, the third message being used to request the addition or modification of the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the service running on the terminal device.

[0222] Optionally, the processing unit 602 is further configured to determine that the service quality of the terminal device or the first service does not meet the user's requirements, or that the service quality of the terminal device or the first service is less than or equal to a threshold value; and to send a fourth message through the communication unit 601, the fourth message being used to indicate the addition or modification of the experience level / communication configuration of the first service.

[0223] The module division in this application embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules. It is understood that the functions or implementations of the modules in the embodiments of this application can be further described in the relevant descriptions of the method embodiments.

[0224] In one possible embodiment, the communication device can be as shown in FIG7. This device can be a communication apparatus or a chip within a communication apparatus, wherein the communication apparatus can be the first device described in the above embodiments. The device includes a processor 701 and a communication interface 702, and may also include a memory 703. The processing unit 602 can be the processor 701. The communication unit 601 can be the communication interface 702. Optionally, the processor 701 and the memory 703 can also be integrated together.

[0225] The processor 701 can be a CPU, a digital processing unit, or something similar. The communication interface 702 can be a transceiver, an interface circuit such as a transceiver circuit, or a transceiver chip, etc. The device also includes a memory 703 for storing the program executed by the processor 701. The memory 703 can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory 703 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but is not limited to this.

[0226] The processor 701 is used to execute the program code stored in the memory 703, specifically to perform the actions of the processing unit 602 described above, which will not be described in detail here. The communication interface 702 is specifically used to perform the actions of the communication unit 601 described above, which will not be described in detail here.

[0227] This application embodiment does not limit the specific connection medium between the communication interface 702, processor 701, and memory 703. In Figure 7, the memory 703, processor 701, and communication interface 702 are connected via a bus 704, which is represented by a thick line. The connection methods between other components are only illustrative and not intended to be limiting. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is used in Figure 7, but this does not indicate that there is only one bus or one type of bus.

[0228] This application also provides a computer-readable storage medium for storing computer software instructions required to execute the processor, including a program required to execute the processor.

[0229] This application also provides a communication system, including a communication device for implementing the terminal device function in the embodiment of FIG5 and a communication device for implementing the network device (e.g., access network device, core network device) function in the embodiment of FIG5.

[0230] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0231] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0232] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0233] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0234] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope and intent of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and variations.

Claims

1. A communication method characterized by comprising: The method comprises: displaying an icon corresponding to a first experience level, the first experience level being an experience level of a terminal device, an experience level of a user using the terminal device, or an experience level of a first service running on the terminal device; wherein different experience levels are mapped to different communication configurations.

2. The method of claim 1, wherein, The method further comprises: receiving a first message, the first message being used to indicate that a first service is supported or enabled by an access network device or a core network device, or the first message indicating that the first service is enabled for the terminal device, a user using the terminal device, or the first service running on the terminal device by the access network device or the core network device; wherein the first service is configured with corresponding communication configurations for experience levels.

3. The method of claim 1 or 2, wherein, The method further comprises: receiving first information, the first information being used to indicate a communication configuration configured for the terminal device, wherein the communication configuration indicated by the first information meets the communication configuration corresponding to the first experience level.

4. The method according to any one of claims 1 to 3, characterized in that, The method further comprises: receiving a second message, the second message carrying experience level information, the experience level information indicating the first experience level.

5. The method according to any one of claims 1 to 4, characterized in that, The method further comprises: sending a third message, the third message being used to request to add or modify the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the first service running on the terminal device.

6. The method according to any one of claims 1 to 5, wherein, The method further comprises: displaying a first prompt, the first prompt being used to prompt the user whether to add or modify the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the first service running on the terminal device.

7. The method of claim 5, wherein, The sending of the third message comprises: in response to a first operation of the user, sending the third message, the first operation being used to confirm to add or modify the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the first service running on the terminal device.

8. The method of claim 5 or 7, wherein, Before the third message is sent, the method further comprises: determining that a quality of service of the terminal device or the first service does not meet a user requirement, or the quality of service of the terminal device or the first service is less than or equal to a threshold value.

9. The method of any one of claims 1-3, wherein, The method further comprises: receiving a fourth message, the fourth message being used to indicate to add or modify the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the first service running on the terminal device.

10. The method of any one of claims 1-9, wherein, The method further comprises: obtaining information of a first service, the information of the first service including communication configurations corresponding to N experience levels respectively, N being an integer greater than 0, the first experience level being one of the N experience levels; wherein the first service is configured with corresponding communication configurations for experience levels, the information of the first service being preconfigured, or the information of the first service being from an access network device or a core network device.

11. A communication method, comprising: The method comprises: sending a second message carrying experience level information, the experience level information indicating an experience level of the terminal device, an experience level of a user using the terminal device, or an experience level of a service running on the terminal device, or sending first information for indicating a communication configuration configured for the terminal device, wherein the communication configuration indicated by the first information meets the communication configuration corresponding to the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the service running on the terminal device.

12. The method of claim 11, wherein, The method further includes: sending a first message for indicating that the access network device or the core network device supports or enables a first service, or the first message indicates that the access network device or the core network device enables the first service for the terminal device, a user using the terminal device, or a service running on the terminal device; wherein the first service is configured with a corresponding communication configuration for an experience level.

13. The method of claim 11 or 12, wherein, The method further includes: sending information of the first service, the information of the first service including N experience levels respectively corresponding to a communication configuration, N being an integer greater than 0, the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the service running on the terminal device being one of the N experience levels; wherein the first service is configured with a corresponding communication configuration for an experience level.

14. The method according to any one of claims 11 to 13, wherein, The method further includes: receiving a third message for requesting to add or modify the experience level of the terminal device, the experience level of the user using the terminal device, or the experience level of the service running on the terminal device.

15. The method of any one of claims 11-13, wherein, The method further includes: determining that a service quality of the terminal device or the first service does not meet a user requirement, or the service quality of the terminal device or the first service is less than or equal to a threshold value; sending a fourth message for indicating to add or modify the experience level / communication configuration of the first service.

16. The method of any one of claims 1-14, wherein, The communication configuration includes at least one of the following: slice resource, QoS configuration, QoE configuration, subnetwork resource, and resource scheduling strategy.

17. The method of claim 16, wherein, The slice resource includes at least one of the following: slice resource of an access network, slice resource of a core network, and slice resource of a transport network.

18. The method of claim 17, wherein, The slice resource of the access network includes at least one of the following: number of dedicated resource blocks (RBs), low-frequency carrier priority enabling, carrier exclusivity enabling, and time domain scheduling priority enabling.

19. The method of claim 17 or 18, wherein, The slice resource of the core network includes at least one of the following: a virtual network function (VNF) network element exclusively occupied, a VNF network element shared by partial slice resources, and a VNF network element shared by all slice resources.

20. The method of any one of claims 17-19, wherein, The slice resource of the transport network includes at least one of the following: transport resource of a transport network, segment routing transport subset (SR-TP) tunnel, SR-TP operation, administration, and management (OAM) detection technology, and re-routing protection.

21. The method of claim 16, wherein, The QoS configuration includes at least one of the following: QoS identifier, allocation retention priority (ARP), guaranteed flow bit rate (GFBR), maximum flow bit rate (MFBR), average maximum flow bit rate (AMBR), reflective QoS (RQA), notification control, and maximum packet loss rate.

22. The method of claim 21, wherein, The QoS identifier is a QoS class identifier QCI or a 5G QoS identifier 5QI.

23. The method of claim 16, wherein, The QOE configuration includes at least one of: uplink guaranteed delay, downlink guaranteed delay, uplink guaranteed rate, downlink guaranteed rate, reliability guarantee, packet loss rate guarantee, guaranteed jitter, task success rate, service success rate, guaranteed code rate, definition, frame rate, resolution, operation response time, call setup delay, handover response delay, two-way end-to-end delay.

24. The method of claim 16, wherein, The resource scheduling strategy includes at least one of: preferentially configuring a large number of resource block RB resources in one scheduling time unit, configuring at least M RB resources in one scheduling time unit, preferentially using a low-order modulation and coding format in one scheduling time unit, and using a modulation and coding format not higher than X in one scheduling time unit, wherein M is an integer greater than 0, and X is a predefined modulation and coding format or a network configured modulation and coding format threshold.

25. The method of any one of claims 1-24, wherein, The experience level is one or more of: slice level, QoS guarantee level, QoE guarantee level, and subnetwork level.

26. A communications device, characterized by A computer program product comprising computer readable instructions arranged to perform the method of any of claims 1-10, 16-25, or the method of any of claims 11-25.

27. A communications device, characterized by A processor configured to cause the method of any of claims 1-10, 16-25, or the method of any of claims 11-25 to be performed.

28. A computer-readable storage medium, characterized in that, A computer readable storage medium having computer readable instructions stored therein, which when executed on a communications device, cause the method of any of claims 1-10, 16-25, or the method of any of claims 11-25 to be performed.

29. A computer program product, characterised in that, A computer program product, which when executed on a device, causes the device to perform the method of any of claims 1-10, 16-25, or the method of any of claims 11-25.

Images