WO2023245458A1

WO2023245458A1 - Information reporting method, apparatus and computer storage medium

Info

Publication number: WO2023245458A1
Application number: PCT/CN2022/100255
Authority: WO
Inventors: 吴锦花; 刘建宁; 沈洋; 张楠; 毛玉欣
Original assignee: 北京小米移动软件有限公司
Priority date: 2022-06-21
Filing date: 2022-06-21
Publication date: 2023-12-28
Also published as: CN117616798A

Abstract

Provided in the embodiments of the present disclosure are an information reporting method, an apparatus and a computer storage medium. The communication method can be applied to a 5G system. The method may comprise: by providing terminal state information of a UE to a network side (comprising an access network side and a core network side), a network being capable of matching service traffic characteristics and terminal energy consumption management according to the terminal state information, that is, executing policy decision-making and execution on a first service according to the power consumption state of the terminal, thereby meeting service requirements and ensuring the user experience. In addition, providing the terminal state information to the access network side is also beneficial for the access network side to perform, according to the state information of the UE, decision-making or updating on at least one of a terminal policy, a service policy for the first service, and a network configuration.

Description

An information reporting method, device and computer storage medium

Technical field

The present disclosure relates to the field of wireless communication technology, and in particular, to an information reporting method, device and computer storage medium.

Background technique

In the fifth generation mobile networks (5G) technology, mobile media services, cloud extended reality (XR), cloud games, video-based machine or drone remote control, etc. are expected to provide 5G network Contribute more and more traffic.

Currently, because media traffic (such as XR/media traffic) has the characteristics of high throughput, low latency, and high reliability requirements, it requires high power consumption on the terminal side, and the battery power of the terminal may affect the user experience.

Then, how to match business traffic characteristics and terminal energy consumption management is an urgent problem that needs to be solved.

Contents of the invention

The present disclosure provides an information reporting method, device and computer storage medium to match business traffic characteristics and terminal energy consumption management, thereby ensuring business requirements and user experience.

According to a first aspect of the present disclosure, an information reporting method is provided, which method can be applied to an access network functional entity in a communication system. The method may include: the access network functional entity receives terminal status information sent by the terminal, and the terminal status information is used to represent the power consumption status of the terminal; the access network functional entity performs at least one of the following: determining the terminal policy according to the terminal status information, At least one of the service policy of the first service and the network configuration; sending terminal status information to the core network functional entity, and the terminal status information is also used by the core network functional entity to determine the terminal policy, the business policy of the first service and the network configuration. At least one.

In the present disclosure, the above-mentioned core network functional entity may include a first core network functional entity, a second core network functional entity, and a fourth core network functional entity.

In some possible implementations, the above method further includes: the access network functional entity receives service indication information sent by the terminal, and the service indicator is used to indicate the first service.

In some possible implementations, the terminal status information includes at least one of the following: battery power; battery life; power supply mode; terminal overheating status.

In some possible implementations, the access network function entity configures a network configuration for a public land mobile network PLMN.

In some possible implementations, the above method further includes: the access network functional entity sends a first request message to the terminal, where the first request message is used to request terminal status information.

In some possible implementations, before the access network functional entity sends the first request message to the terminal, the above method further includes: the access network functional entity receives a second request message sent by the core network functional entity, and the second request message is For requesting terminal status information; after the access network functional entity receives the terminal status information sent by the terminal, the above method further includes: the access network functional entity sends the terminal status information to the core network functional entity.

In some possible implementations, the access network functional entity determines at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information, including: the access network functional entity determines the terminal status information and the terminal configuration. The matching situation of at least one of the policy, the service policy of the first service and the network configuration; the access network function entity determines at least one of the corresponding terminal policy, the service policy of the first service and the network configuration according to the matching situation.

In the present disclosure, the access network functional entity determines the matching between the terminal status information and at least one of the terminal policy, the service policy of the first service, and the network configuration, including: the access network functional entity determines the terminal status information based on the terminal status information. Whether to support the first capability, which is the capability required by the first service; the access network functional entity determines at least one of the terminal policy, the service policy of the first service and the network configuration according to the matching situation, including: if the terminal If the first capability is supported, the access network functional entity determines at least one of the first terminal policy, the first service policy of the first service, and the first network configuration; if the terminal does not support the first capability, the access network functional entity At least one of a second terminal policy, a second service policy of the first service, and a second network configuration is determined.

In some possible implementations, the access network functional entity determines at least one of the terminal policy, the service policy of the first service, and the network configuration based on the terminal status information, including: the access network functional entity determines based on the terminal status information Whether the terminal supports the first capability, the first capability is the capability required by the first service; if the terminal supports the first capability, the access network functional entity determines the first service policy and/or the first network configuration of the first service; if If the terminal does not support the first capability, the access network functional entity determines the second service policy and/or the second network configuration of the first service.

In some possible implementations, the terminal status information is carried in a first radio resource control (RRC) message, and the first RRC message is used to trigger the terminal to switch from the inactive state to the connected state.

In some possible implementations, the above method further includes: the access network functional entity receives a third request message sent by the core network functional entity, and the third request message is used to request a terminal status information notification message; the access network functional entity sends a third request message to the core network functional entity. The functional entity sends a terminal status information notification message, and the terminal status information notification message carries terminal status information.

In some possible implementations, the terminal status information is carried in access network (access network, AN) parameters; or, the terminal status information is carried in AN parameters and non-access stratum (non-access stratum, NAS) parameters.

In some possible implementations, in response to the terminal status information being carried in the AN parameter, the access network functional entity sends the terminal status information to the core network functional entity, including: the access network functional entity taking the terminal status information out of the AN parameter; The access network functional entity carries the terminal status information in the NAS parameter and sends it to the core network functional entity.

In some possible implementations, the access network functional entity carries the terminal status information in NAS parameters and sends it to the core network functional entity, including: the access network functional entity determines the terminal status information according to the terminal policy, the service policy of the first service, and the network configuration. At least one of them adds the terminal status information to the NAS parameter; the access network functional entity carries the NAS parameter in the NAS message and sends it to the core network functional entity.

In some possible implementations, in response to the terminal status information being carried in AN parameters and non-access layer NAS parameters, the AN parameters and NAS parameters are carried in messages in the packet data unit (packet data unit, PDU) session establishment process; and /Or, the AN parameter and the NAS parameter are carried in the message during the registration process.

In some possible implementations, the above method further includes: the access network functional entity saves the terminal status information.

In some possible implementations, the first service is an extended reality and media (XRM) service.

According to a second aspect of the present disclosure, an information reporting method is provided, which method can be applied to a first core network functional entity in a communication system. The method includes: the first core network functional entity receives terminal status information sent by the access network functional entity, the terminal status information is used to represent the power consumption status of the terminal; the first core network functional entity performs at least one of the following: according to the terminal status information , determine at least one of the terminal policy, the service policy of the first service, and the network configuration; send terminal status information to the second core network functional entity, and the terminal status information is also used for the second core network functional entity and/or the fourth core The network function entity determines at least one of the terminal policy, the service policy of the first service, and the network configuration.

In some possible implementations, the above method further includes: the first core network functional entity receiving service indication information sent by the access network functional entity, where the service indicator is used to indicate the first service.

In some possible implementations, before the first core network functional entity receives the terminal status information sent by the access network functional entity, the above method further includes: the first core network functional entity sends a first request message to the access network device, The first request message is used to request terminal status information of the terminal.

In some possible implementations, the first core network functional entity receives terminal status information sent by the access network functional entity, including: the first core network functional entity receives NAS parameters sent by the access network functional entity, and the NAS parameters carry the terminal status information.

In some possible implementations, before the first core network functional entity sends the terminal status information to the second core network functional entity, the above method further includes: the first core network functional entity determines that the subscription information of the terminal needs to include terminal status information. .

In some possible implementations, the first core network functional entity sends terminal status information to the second core network functional entity, including: the first core network functional entity queries event subscriptions and confirms subscription to the first event associated with the terminal status information; When the event reporting conditions are met, the first core network functional entity sends the terminal status information to the second core network functional entity.

In some possible implementations, the first event is subscribed to by the second core network functional entity.

In some possible implementations, the first event is subscribed by the second core network functional entity to the third core network functional entity;

The first core network functional entity sends terminal status information to the second core network functional entity, including: after the terminal is switched from the third core network functional entity to the first core network functional entity, the first core network functional entity sends the terminal status information to the second core network functional entity. Functional entities send terminal status information.

In some possible implementations, the above method further includes: the first core network functional entity receiving at least one of the terminal policy, the service policy of the first service, and the network configuration sent by the second core network functional entity, the terminal policy, the first service policy, and the network configuration. At least one of the service policy and network configuration of a service is generated or updated by the second core network functional entity based on the terminal status information.

In some possible implementations, the above method further includes: the first core network functional entity saves the terminal status information.

In some possible implementations, the first service is an XRM service.

According to a third aspect of the present disclosure, an information reporting method is provided, which method can be applied to a fourth core network functional entity in a communication system. The method includes: a fourth core network functional entity receives terminal status information sent by the first core network functional entity, the terminal status information is used to represent the power consumption status of the terminal; the fourth core network functional entity performs at least one of the following: according to the terminal status information to determine at least one of the terminal policy, the service policy of the first service and the network configuration; send terminal status information to the second core network functional entity, and the terminal status information is also used by the second core network functional entity to determine the terminal policy, the third At least one of a service policy and a network configuration.

In some possible implementations, the above method further includes: a fourth core network functional entity receiving service indication information sent by the first core network functional entity, where the service indicator is used to indicate the first service.

In some possible implementations, the fourth core network functional entity determines at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information, including: the fourth core network functional entity determines at least one of the terminal policy according to the terminal status information. information and the terminal's subscription information and/or service policy to determine the policy of the PDU session.

In some possible implementations, the fourth core network functional entity receives the terminal status information sent by the first core network functional entity, including: the fourth core network functional entity receives the NAS parameter sent by the first core network device, and the NAS parameter carries Terminal status information.

In some possible implementations, the above method further includes: the fourth core network functional entity saves the terminal status information.

In some possible implementations, the first service is an XRM service.

According to a fourth aspect of the present disclosure, an information reporting method is provided, which method can be applied to the second core network functional entity in the communication system. The method includes: the second core network functional entity receives terminal status information, and the terminal status information is used to represent the power consumption status of the terminal; the second core network functional entity determines the terminal policy, the business policy of the first service, and the network based on the terminal status information. At least one of the configuration.

In some possible implementations, the above method further includes: the second core network functional entity receives service indication information, and the service indicator is used to indicate the first service.

In some possible implementations, the second core network functional entity receives the terminal status information, including: the second core network functional entity receives the terminal status information sent by the first core network functional entity and/or the fourth core network functional entity; One core network functional entity is used for mobility management, and a fourth core network functional entity is used for session management.

In some possible implementations, the above method further includes: the second core network functional entity updates at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information; the second core network functional entity reports to One or more of the first core network functional entity, the fourth core network functional entity, the access network functional entity and the terminal sends at least one of the updated terminal policy, the service policy of the first service and the network configuration.

According to the fifth aspect of the present disclosure, a communication device is provided. The communication device can be an access network functional entity in a communication system or a chip or system-on-chip of an access network functional entity. It can also be a communication device used in an access network functional entity. Functional modules that implement the methods described in the above embodiments. The communication device can realize the functions performed by the access network functional entities in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions. The device may include: a receiving module configured to receive terminal status information sent by the terminal, where the terminal status information is used to represent the power consumption status of the terminal; a processing module configured to determine the terminal policy and the first service based on the terminal status information. At least one of service policy and network configuration; the sending module is configured to send terminal status information to the core network functional entity, and the terminal status information is also used by the core network functional entity to determine the terminal policy, the business policy of the first service, and the network configuration at least one of them.

In some possible implementations, the receiving module is also configured to receive service indication information sent by the terminal, and the service indicator is used to indicate the first service.

In some possible implementations, the sending module is further configured to send a first request message to the terminal, where the first request message is used to request terminal status information.

In some possible implementations, the receiving module is further configured to receive a second request message sent by the core network functional entity before the sending module sends the first request message to the terminal, where the second request message is used to request terminal status information; The sending module is further configured to send the terminal status information to the core network functional entity after the receiving module receives the terminal status information sent by the terminal.

In some possible implementations, the processing module is also configured to determine a match between the terminal status information and at least one of the terminal policy, the service policy of the first service, and the network configuration; and determine the corresponding terminal policy based on the match. , at least one of the service policy of the first service and the network configuration.

In the present disclosure, the processing module is also configured to: determine whether the terminal supports the first capability according to the terminal status information, and the first capability is the capability required by the first service; determine the terminal policy and the first service according to the matching situation. At least one of the service policy and the network configuration includes: if the terminal supports the first capability, determining at least one of the first terminal policy, the first service policy of the first service, and the first network configuration; if the terminal does not support The first capability determines at least one of the second terminal policy, the second service policy of the first service, and the second network configuration.

In some possible implementations, the processing module is further configured to determine, based on the terminal status information, whether the terminal supports the first capability, where the first capability is the capability required by the first service; if the terminal supports the first capability, determine whether the terminal supports the first capability. A terminal policy, at least one of the first service policy of the first service and the first network configuration; if the terminal does not support the first capability, determine the second terminal policy, the second service policy of the first service and the second network At least one of the configuration.

In some possible implementations, the terminal status information is carried in the first RRC message, and the first RRC message is used to trigger the terminal to switch from the inactive state to the connected state.

In some possible implementations, the receiving module is also configured to receive a third request message sent by the core network functional entity. The third request message is used to request a terminal status information notification message; the sending module is also configured to send a third request message to the core network function entity. The entity sends a terminal status information notification message, and the terminal status information notification message carries terminal status information.

In some possible implementations, the terminal status information is carried in AN parameters; or, the terminal status information is carried in AN parameters and NAS parameters.

In some possible implementations, in response to the terminal status information being carried in the AN parameter, the sending module is further configured to extract the terminal status information from the AN parameter; and carry the terminal status information in the NAS parameter and send it to the core network functional entity.

In some possible implementations, the sending module is also configured to add the terminal status information to the NAS parameters according to at least one of the terminal policy, the service policy of the first service, and the network configuration; and carry the NAS parameters in the NAS message to Sent by the core network functional entity.

In some possible implementations, in response to the terminal status information being carried in AN parameters and non-access layer NAS parameters, the AN parameters and NAS parameters are carried in messages during the PDU session establishment process; and/or, the AN parameters and NAS parameters are carried Yu is a message during the registration process.

In some possible implementations, the processing module is also configured to save terminal status information.

In some possible implementations, the first service is an XRM service.

According to a sixth aspect of the present disclosure, a communication device is provided. The communication device may be the first core network functional entity in the communication system or a chip or system-on-chip of the first core network functional entity. It may also be the first core network functional entity. The functional modules used to implement the methods described in the above embodiments. The communication device can realize the functions performed by the first core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions. The device may include: a receiving module configured to receive terminal status information sent by the access network functional entity, where the terminal status information is used to represent the power consumption status of the terminal; a processing module configured to determine the terminal policy, At least one of the service policy of the first service and the network configuration; the sending module is configured to send terminal status information to the second core network functional entity and/or the fourth core network functional entity, and the terminal status information is also used for the second core network functional entity. The core network functional entity determines at least one of the terminal policy, the service policy of the first service, and the network configuration.

In some possible implementations, the receiving module is further configured to receive service indication information sent by the access network functional entity, where the service indicator is used to indicate the first service.

In some possible implementations, the sending module is also configured to send a first request message to the access network device before the receiving module receives the terminal status information sent by the access network functional entity. The first request message is used to request the terminal. terminal status information.

In some possible implementations, the receiving module is also configured to receive NAS parameters sent by the access network functional entity, where the NAS parameters carry terminal status information.

In some possible implementations, the processing module is further configured to determine that the subscription information of the terminal needs to include terminal status information before the sending module sends the terminal status information to the second core network functional entity.

In some possible implementations, the processing module is also configured to query event subscriptions and confirm the first event associated with the subscribed terminal status information; the sending module is also configured to send a message to the second core when event reporting conditions are met. The network function entity sends terminal status information.

In some possible implementations, the first event is subscribed by the second core network functional entity to the third core network functional entity; the sending module is also configured to switch from the third core network functional entity to the first core network at the terminal. After entering the functional entity, the terminal status information is sent to the second core network functional entity.

In some possible implementations, the receiving module is further configured to receive at least one of the terminal policy, the service policy of the first service, and the network configuration sent by the second core network functional entity. At least one of the policy and the network configuration is updated by the second core network functional entity based on the terminal status information.

In some possible implementations, the first service is an XRM service.

According to a seventh aspect of the present disclosure, a communication device is provided. The communication device may be the fourth core network functional entity in the communication system or a chip or system-on-chip of the fourth core network functional entity. It may also be the fourth core network functional entity. The functional modules used to implement the methods described in the above embodiments. The communication device can realize the functions performed by the fourth core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions. The device may include: a receiving module configured to receive terminal status information sent by the first core network functional entity, where the terminal status information is used to represent the power consumption status of the terminal; a processing module configured to determine a terminal policy based on the terminal status information , at least one of the service policy of the first service and the network configuration; the sending module is configured to send terminal status information to the second core network functional entity, and the terminal status information is also used by the second core network functional entity to determine the terminal policy, At least one of the service policy of the first service and the network configuration.

In some possible implementations, the receiving module is further configured to receive service indication information sent by the first core network functional entity, where the service indicator is used to indicate the first service.

In some possible implementations, the processing module is further configured to determine the policy of the PDU session based on the terminal status information and the terminal's subscription information and/or service policy.

In some possible implementations, the receiving module is configured to receive NAS parameters sent by the first core network device, where the NAS parameters carry terminal status information.

In some possible implementations, the first service is an XRM service.

According to an eighth aspect of the present disclosure, a communication device is provided. The communication device may be the second core network functional entity in the communication system or a chip or system-on-chip of the second core network functional entity. It may also be the second core network functional entity. The functional modules used to implement the methods described in the above embodiments. The communication device can realize the functions performed by the second core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions. The device may include: a receiving module configured to receive terminal status information, the terminal status information is used to represent the power consumption status of the terminal; a processing module configured to determine the terminal policy, the service policy of the first service according to the terminal status information; At least one of the network configurations.

In some possible implementations, the receiving module is configured to receive service indication information, and the service indicator is used to indicate the first service.

In some possible implementations, the receiving module is further configured to receive terminal status information sent by the first core network functional entity and/or the fourth core network functional entity, the first core network functional entity being used for mobility management, and the Four core network functional entities are used for session management.

In some possible implementations, the above device further includes: a sending module; a processing module, further configured to update at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information; the sending module, Configured to send at least one of the updated terminal policy, the service policy of the first service and the network configuration to the first core network functional entity, the fourth core network functional entity, the access network functional entity and the terminal.

According to a ninth aspect of the present disclosure, a communication device, such as an access network functional entity, is provided, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored in the memory to implement The method described in the above first aspect and any possible implementation thereof.

According to a tenth aspect of the present disclosure, a communication device, such as a first core network functional entity, is provided, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored in the memory to Implement the method described in the above second aspect and any possible implementation manner thereof.

According to an eleventh aspect of the present disclosure, a communication device, such as a fourth core network functional entity, is provided, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored in the memory, To implement the method described in the above third aspect and any possible implementation manner thereof.

According to a twelfth aspect of the present disclosure, a communication device, such as a second core network functional entity, is provided, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored in the memory, To implement the method described in the fourth aspect and any possible implementation manner thereof.

According to a thirteenth aspect of the present disclosure, a computer-readable storage medium is provided. Instructions are stored in the computer-readable storage medium; when the instructions are run on a computer, they are used to perform the above-mentioned first to fourth aspects and any of the possibilities thereof. The method described in the embodiment.

According to a fourteenth aspect of the present disclosure, a computer program or computer program product is provided. When the computer program product is executed on a computer, the computer implements the above described first to fourth aspects and any possible implementation manner thereof. method.

In this disclosure, by providing the terminal status information of the UE to the network side (including the access network side and the core network side), the network can match the service traffic characteristics and terminal energy consumption management according to the terminal status information, that is, according to the power consumption of the terminal. The state implements strategic decisions and execution for the first business to ensure business needs and user experience. At the same time, the terminal status information is provided to the access network side, which also facilitates the access network side to make decisions or update at least one of the terminal policy, the service policy of the first service, and the network configuration based on the UE status information.

It should be understood that the fifth to fourteenth aspects of the present disclosure are consistent with the technical solutions of the first to fourth aspects of the present disclosure, and the beneficial effects achieved by each aspect and corresponding feasible implementations are similar, and will not be described again.

Description of the drawings

Figure 1 is an architectural schematic diagram of a 5G communication system in an embodiment of the present disclosure;

Figure 2 is a schematic flowchart of the implementation of the first status information reporting method in an embodiment of the present disclosure;

Figure 3 is a schematic flowchart of the implementation of the second status information reporting method in the embodiment of the present disclosure;

Figure 4 is a schematic flowchart of the implementation of the third status information reporting method in an embodiment of the present disclosure;

Figure 5 is a schematic flowchart of the implementation of the fourth status information reporting method in an embodiment of the present disclosure;

Figure 6 is a schematic structural diagram of a communication device in an embodiment of the present disclosure;

Figure 7 is a schematic structural diagram of another communication device in an embodiment of the present disclosure;

Figure 8 is a schematic structural diagram of a network functional entity in an embodiment of the present disclosure.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings refer to the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with embodiments of the present disclosure. Rather, they are merely examples of apparatus and methods consistent with aspects of embodiments of the present disclosure as detailed in the appended claims.

The terminology used in the embodiments of the present disclosure is for the purpose of describing specific embodiments only and is not intended to limit the embodiments of the present disclosure. As used in the embodiments of the present disclosure and the appended claims, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise. It will also be understood that the term "and/or" as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms “first”, “second”, “third”, etc. may be used to describe various information in the embodiments of the present disclosure, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other. For example, without departing from the scope of the embodiments of the present disclosure, "first information" may also be called "second information", and similarly, "second information" may also be called "first information". Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to determining."

Further, in the description of the embodiments of the present disclosure, "and/or" is only an association relationship describing associated objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of the present disclosure, "plurality" may refer to two or more than two.

The technical solution of the embodiment of the present disclosure relates to the architecture of a communication system. The communication system may be a 5G communication system or a future evolution communication system. In the architecture of the communication system, there are terminals, access network functional entities (which can also be described as access network functional entities, access network elements, access network functional components, access network functional modules, etc.) and at least one core Network function (NF) entity (can also be described as core network equipment, core network element, core network functional component, core network functional module, etc.). At least one core network functional entity is located in the core network (ie 5GC). The terminal is used to report terminal status information (UE status information) used to indicate its own power consumption status to the network side; the access network functional entity and at least one core network functional entity have at least the following functions: according to the received terminal status information, determine At least one of the terminal policy, the service policy of the first service, and the network configuration; and forwarding the terminal device information to a lower-level core network functional entity. In practical applications, the first service may include XR service, mobile media service, etc., wherein XR service and mobile media service may also be called XRM service, or may also be described as XR\M service.

In the following, the embodiments of the present disclosure will be explained and described, taking a 5G communication system as an example. It should be noted that the embodiments of the present disclosure are also applicable to any future evolution communication system after the 5G communication system, and the embodiments of the present disclosure do not specifically limit this.

Figure 1 is an architectural schematic diagram of a 5G communication system in an embodiment of the present disclosure. Referring to Figure 1, the above-mentioned 5G communication system 100 may include a 5G Radio Access Network (RAN) and a 5G Core Network (5GC). The 5G wireless access network may include next generation radio access network (NG RAN). NG RAN 101 communicates with the terminal (or terminal device) 102 through the Uu interface. The 5G core network 103 may include: at least one core network functional entity mentioned above, such as access and mobility management function (AMF) entity 1031, session management function (SMF) entity 1032, and policy control Function (policy control function, PCF) entity 1033, etc. In the embodiment of the present disclosure, the above communication system may also include other network elements, which is not specifically limited in the embodiment of the present disclosure.

In the embodiment of the present disclosure, in the above-mentioned 5G communication system 100, the following interfaces may be provided between each core network functional entity:

N7 is the interface between PCF and SMF and is used to deliver PDU session granularity and service data flow granularity control policies.

N15 is the interface between PCF and AMF, which is used to download terminal policies and access control-related policies.

N11 is the interface between SMF and AMF, used to deliver control messages sent to UE, radio resource control information sent to NG RAN, etc.

N2 is the interface between AMF and NG RAN, and is used to transmit wireless bearer control information from the core network side to NG RAN.

N1 is the interface between AMF and UE, which has nothing to do with access. It is used to deliver QoS control rules to UE.

The above-mentioned terminal may be a terminal device with a wireless communication function and a wireless sensing function, and may also be called user equipment (UE). Terminals can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; they can also be deployed on water (such as ships, etc.); they can also be deployed in the air (such as aircraft, balloons, satellites, etc.). The terminal can be a mobile phone, a tablet computer, a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, or an industrial control (industrial control) ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc. The terminal may also be a handheld device, a vehicle-mounted device, a wearable device, a computing device, or other processing device connected to a wireless modem with wireless communication functions and wireless sensing functions. Optionally, the terminal device can also be called by different names in different networks, for example: terminal device, access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile equipment, user terminal , terminal, wireless communication equipment, user agent or user device, cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital processing (personal digital) assistant, PDA), 5G communication system or terminals in future evolution communication systems, etc.

The above-mentioned access network functional entity may be a functional entity used by the access network side to support communication terminals to access the wireless communication system. For example, it can be the next generation base station (next generation NodeB, gNB), transmission reception point (TRP), relay node (relay node), access point (AP), etc. in the 5G communication system.

It should be noted that in the communication system shown in FIG. 1 , each functional entity and interface are only exemplary, and not all functions of each functional entity are necessary when applied in the embodiments of the present disclosure. The functional entities of the access network and core network may be physical physical devices or virtualized devices, which are not limited here. Of course, the communication system in the embodiment of the present disclosure may also include other devices not shown in Figure 1, which are not limited here.

In 5G networks, mobile media services, XR, cloud games, video-based machine or drone remote control, etc. are expected to contribute more and more traffic to 5G networks. Especially XR and media (extend reality and media, XRM) business. XRM business has the characteristics of high throughput, low latency, and high reliability requirements, and requires high power consumption on the terminal side. The battery power of the terminal may affect the user experience.

Currently, based on existing terminal implementations and considering service traffic characteristics, a terminal power saving enhancement solution has been defined in 3GPP. For example, the power saving mode of the terminal in different connection states (connection management, CM), such as the power saving mode of CM-IDLE (idle state) and the power saving mode of CM-CONNECTED (connected) in the RRC inactive state. Defines mobile initiated connection only (MICO) mode, extended discontinuous reception (extended DRX, eDRX) mode, etc. However, the above solutions are specially designed for IoT terminals with ultra-low power consumption. If these solutions are used on smartphones, the user experience will be greatly affected.

Therefore, how to match business traffic characteristics and terminal energy consumption management is an urgent problem that needs to be solved.

In the embodiments of the present disclosure, in the following embodiments, the terminal device in the communication system may be a UE as an example, the access network functional entity may be a base station as an example, the first core network functional entity may be an AMF as an example, and the second core network functional entity may be an AMF as an example. Taking the network functional entity as PCF as an example and the fourth core network functional entity as SMF, the terminal status information method proposed in the embodiment of the present disclosure will be described. In the 5G communication system and its evolved versions, the terminal, access network functional entity, first core network functional entity, second core network functional entity and fourth core network functional entity may also have the same or similar functions and connection relationships. Other functional entities are not limited in this embodiment of the disclosure.

In order to solve the above problem, in combination with the above communication system, embodiments of the present disclosure provide an information reporting method.

Figure 2 is a schematic flowchart of the implementation of the first status information reporting method in an embodiment of the present disclosure. As shown in Figure 2, in this embodiment, the information reporting method is applied to the access network functional entity (such as a base station) side. The information reporting method may include S201 to S204.

S201. The base station receives terminal status information (UE status information) sent by the terminal (such as UE).

The terminal status information is used to indicate the power consumption status of the UE. Exemplarily, the terminal status information includes one or more parameters related to the UE performance. For example, the UE status information may include at least one of the following: UE battery level, UE battery life, UE’s power supply mode (powered mode) and UE overheating status (UE overheating status). Of course, in this embodiment of the present disclosure, parameters related to UE power consumption may include other parameters. Here, the power supply mode of the UE may include: battery-powered mode (battery-powered) and power supply mode (mains/wall-powered).

After S201, the base station performs at least one of S202 to S203:

S202: The base station determines at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information.

It can be understood that after receiving the terminal status information of the UE, the base station can make business policy decisions and/or set network configurations according to the power consumption status of the UE. Here, the terminal policy, the service policy of the first service and the network configuration may be related to the access behavior of the UE.

Here, the base station sets a network configuration (can also be understood as network configuration information) for a PLMN.

In this embodiment of the present disclosure, the first service may be an XRM service or an XRM service group.

In some possible implementations, the above-mentioned terminal policy, service policy of the first service and network configuration may be of different granularities, for example, they may be for the UE, for the service, or for the session. The embodiments of this disclosure are for This is not specifically limited.

It can be understood that the base station can determine at least one of the corresponding terminal policy, the service policy of the first service, and the network configuration for all services of the UE (ie, the first service) based on the terminal status information; or, the base station can determine at least one of the corresponding terminal policies according to the terminal status information. The information may be targeted at one or more services of the UE (i.e., the first service) and determine at least one of the corresponding terminal policy, the service policy of the first service, and the network configuration; or, the base station may be targeted at the UE based on the terminal status information. One or more sessions of a service (ie, the first service), and at least one of the corresponding terminal policy, the service policy of the first service, and the network configuration are determined. Alternatively, based on the terminal status information, the base station may determine at least one of the corresponding terminal policy, the service policy of the first service, and the network configuration for one or more sessions of one or more services (ie, the first service) of the UE. .

In some possible implementations, in S202, in order to support the first service, the base station needs to determine the matching between the terminal status information of the UE and at least one of the terminal policy, the service policy of the first service, and the network configuration (it may also be Describe compatibility situation, adaptation situation, etc.), and determine at least one of the corresponding terminal policy, the service policy of the first service, and the network configuration according to the matching situation.

It should be understood that after receiving the terminal status information of the UE, the base station determines the matching between the terminal status information and at least one of each terminal policy of the first service, the service policy of the first service and the network configuration, and selects a It is better to match at least one of the terminal policy, the service policy of the first service and the network configuration, and then execute the first service according to at least one of the selected terminal policy, the service policy of the first service and the network configuration. to match the service traffic characteristics of the first service and the power consumption status of the UE.

In an embodiment, the base station may determine at least one of the terminal policies of the UE and the first service, the service policy of the first service, and the network configuration based on whether the UE has the capabilities required to support the first service (ie, the first capability). one of the matching situations. Wherein, if the UE supports the first capability, the base station determines the first service policy and/or the first network configuration of the first service; if the UE does not support the first capability, the base station determines the second service policy and/or the first service Second network configuration. That is to say, for different capabilities of the UE, the base station can determine at least one of different terminal policies, service policies of the first service, and network configurations. For example, assuming that the first business is the XRM business, it is assumed that the first capability is that the battery power is higher than 50%. If the terminal status information indicates that the current power of the UE is 20%, then the base station can determine that the UE does not support the first capability. At this time, the base station can decide not to send the XRM downlink data stream to the UE and to send the XRM downlink data stream to the UE at a low speed. The UE sends the XRM downlink data flow and other service policies to the UE according to the first QoS. On the contrary, if the terminal status information indicates that the current power of the UE is 70%, then the base station can determine that the UE supports the first capability. At this time, the base station can decide to send the XRM downlink data stream to the UE and send the XRM downlink data stream to the UE at high speed. UE and other business strategies.

Of course, there may be other situations for at least one of the terminal status information and the terminal policy, the service policy of the first service, and the network configuration, which are not specifically limited in the embodiments of the present disclosure.

S203: The base station sends terminal status information to the first core network functional entity (such as AMF).

Here, the terminal status information is also used by the AMF to determine at least one of the terminal policy (UE policy), the service policy of the first service, and the network configuration.

It is understandable that after receiving the terminal status information of the UE, the base station can also forward the information to the core network side, so that the AMF on the core network side can make terminal policy (UE policy) decisions and first services based on the terminal status information. Make business policy decisions and set up at least one of the network configurations.

In some possible implementations, the base station can perform both S202 and S203. It can be understood that when executing S202, the base station can also determine that the terminal status information of the UE needs to be reported to the core network side according to the locally saved service policy or network configuration of the first service. At this time, the base station executes S203 to report the terminal status information to the core network side. The network side provides terminal status information of the UE.

In some possible implementations, the UE reporting terminal status information to the base station may be, but is not limited to, the following trigger situations:

In the first trigger situation, the UE makes its own decision to report its own terminal status information to the base station.

For example, in the UE in the inactive state (CM_Inactive) triggering the connection recovery process (Connection Resume in RRC Inactive), the UE can carry the terminal status information in the RRC message (ie, the first RRC message) sent to the base station to achieve Reporting of terminal status information. Alternatively, when the UE initiates the PDU Session Establishment process (PDU Session Establishment), the UE can carry the terminal status information in the access network (AN) message sent to the base station to report the terminal status information. Furthermore, during the registration process initiated by the UE (Rregistration procedure), the UE can carry terminal status information in the AN message sent to the base station to implement reporting of terminal status information.

In the second trigger situation, the base station requests the UE to report terminal status information.

Exemplarily, the base station sends a first request message to the UE to request terminal status information of the UE. The UE responds to the first request message, performs S201, and sends its own terminal status information to the base station. Optionally, the first request message may be a terminal status information inquiry message (UE status information enquiry), or the first request message may be a terminal status information request message (UE status information request).

In one embodiment, terminal status information is transmitted between the UE and the base station through RRC messages (which can also be described as AN messages).

In the third trigger situation, the core network side requests the UE to report status information.

For example, if AMF, SMF or PCF requires terminal status information to set (can also be described as determining, coordinating, updating, etc.) the first service, then AMF, SMF or PCF can send a second request message to the UE to request the UE's Terminal status information. The UE responds to the second request message, performs S201, and provides its own terminal status information to the core network side through the base station.

It should be noted that, in one embodiment, when the UE provides terminal status information to the AMF, the UE may carry the terminal status information in an RRC message and first send it to the base station, and then the base station sends it to the AMF through an N2 message. Alternatively, the terminal status information is carried in the N1 message and sent to the AMF through the base station. In another embodiment, when the UE provides terminal status information to the SMF, the UE may carry the terminal status information in an RRC message and send it to the base station first, and then the base station sends it to the AMF through the N2 message, and then the AMF sends it to the base station.

SMF. Alternatively, the terminal status information is carried in the N1 message and sent to the AMF through the base station, and then the AMF sends it to the SMF. In another embodiment, when the UE provides terminal status information to the PCF, the UE may carry the terminal status information in an RRC message and first send it to the base station, and then the base station sends it to the AMF through an N2 message, and the AMF then sends it to the PCF. Alternatively, the UE may carry the terminal status information in an RRC message and first send it to the base station, and then the base station sends it to the AMF through the N2 message, and then the AMF sends it to the SMF, and then the SMF sends it to the PFC. Alternatively, the terminal status information is carried in the N1 message and sent to the AMF through the base station, and then sent to the PCF by the AMF and/or SMF. Of course, the UE can also provide terminal status information to different network functional entities on the core network side through other paths, so that these network functional entities can make business policy decisions and network configuration settings based on the terminal status information. This is not specifically limited in the embodiments of the present disclosure. .

For example, the above-mentioned RRC message may be a registration request message during the registration process, a PDU session establishment request message during the PDU establishment process, an RRC message during the connection recovery process initiated by the inactive UE, etc. The N2 message can be a registration request message during the registration process, a PDU session establishment request message during the PDU establishment process, an RRC message during the connection recovery process initiated by an inactive UE, etc.

In some possible implementations, in S201 and S203, the terminal status information of the UE may be sent to the first core network functional entity, such as the AMF, in the following manner, but is not limited to.

In the first method, the UE can carry the AN parameters including the terminal status information in the RRC message and send it to the base station, and then the base station takes the terminal status information out of the AN parameters and adds the NAS parameters. The base station carries the NAS parameters including the terminal status information in the NAS message (such as the N2 message) and sends it to the AMF. At this time, the UE only sends AN parameters to the network side and reports terminal status information through the AN parameters.

In the second method, the UE can carry the AN parameters including the terminal status information in the RRC message and send it to the base station, and the UE can carry the NAS parameters including the terminal status information in the NAS message (such as N1 message, N2 message, etc.) and send it. To AMF. At this time, the UE sends AN parameters and NAS parameters to the network side at the same time, and reports terminal status information to the access network side and core network side through the AN parameters and NAS parameters respectively.

Optionally, the above-mentioned RRC message and NAS message may be messages during the registration process or the PDU session establishment process. Of course, it can also be messages in other processes, and this embodiment of the present disclosure does not specifically limit this.

In some possible implementations, in S201, while sending terminal status information to the base station, the UE may also send service indicator information (service indicator) to the base station to indicate the first service. It can be understood that after the base station receives the service indicator, it can determine the first service according to the service indicator information, and then perform S202.

In some possible implementations, as shown in Figure 2, after S201, the above method may further include:

S204: The base station saves the terminal status information for the base station to determine at least one of the terminal policy of other processes associated with the first service, the service policy of the first service, and the network configuration. Of course, it can also be used to perform S203. Exemplarily, the base station stores the terminal status information in the 5G system mobility management (5GS mobility management, 5GMM) context.

In some possible implementations, embodiments of the present disclosure also provide an information reporting method. Figure 3 is a schematic flowchart of the implementation of the second status information reporting method in an embodiment of the present disclosure. As shown in Figure 3, in this embodiment, the information reporting method is applied to the first core network functional entity (such as AMF) side. The information reporting method may include S301 to S304. Here, AMF is the serving AMF of the UE (serving AMF)

S301. The first core network functional entity (such as AMF) receives the terminal status information sent by the access network functional entity (such as the base station).

In some possible implementations, the base station sends the terminal status information reported by the UE to the AMF. Here, the base station may send the terminal status information reported by the UE to the AMF after receiving the terminal status information reported by the UE, or the base station may respond to the request of the AMF and send the previously saved terminal status information of the UE to the AMF. The base station may also periodically send the UE's terminal status information to the AMF. Of course, the base station may also send the terminal status information of the UE to the AMF in other situations, and this is not specifically limited in the embodiments of the present disclosure.

In one embodiment, the base station sends the terminal status information to the AMF through the NAS parameter. That is to say, the base station carries the terminal status information in the NAS parameter and sends it to the AMF. For example, NAS parameters are carried in N2 messages, such as terminal status information response messages (UE status information response), registration request messages (registration request), etc.

In some possible implementations, based on the third triggering situation in the above embodiment, still referring to FIG. 3 , before S301, the above method may also include:

S304. The AMF sends a first request message (such as UE status information enquiry, UE status information request) to the base station.

Here, the first request message is used to request terminal status information of the UE.

In some possible implementations, in S304, the AMF may also send a third request message (such as UE status information notification request) to the base station to request a terminal status information notification message. The base station sends a terminal status information notification message (UE status information notification) to the AMF, which carries terminal status information.

In some possible implementations, the above method further includes: the AMF saving terminal status information for the AMF to determine at least one of the terminal policies of other processes associated with the first service, the service policy of the first service, and the network configuration, Of course, it can also be used to execute S303.

It should be noted that the implementation process of S304 can refer to the description of the third triggering situation in the embodiment of FIG. 2, and will not be described again here.

In some possible implementations, in S301, while sending the terminal status information to the AMF, the base station may also send service indication information to the AMF to indicate the first service. It can be understood that after the AMF receives the service indicator, it can determine the first service according to the service indication information, and then perform S302.

After S301, AMF may perform at least one of S302 to S303:

S302: The AMF determines at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information.

It should be understood that after receiving the terminal status information, the AMF determines at least one of the terminal policy, the service policy of the first service, and the network configuration according to the power consumption status of the UE. Here the service policy and network configuration can be related to the mobility of the UE.

It should be noted that the execution processes of S302 and S202 are similar. For the implementation process of S302, please refer to the description of S202 in the embodiment of FIG. 2 and will not be described again here.

S303. The AMF sends terminal status information to the PCF and/or the fourth core network functional entity (such as SMF).

Here, the terminal status information is also used by the PCF and/or the SMF to determine at least one of the terminal policy, the service policy of the first service, and the network configuration. For example, policy decisions of XRM business or business groups, QoS authorization of XRM business data flow (service dataflow, SDF).

It can be understood that after receiving the terminal status information of the UE, the AMF can also forward the information to another core network functional entity, such as PCF and/or SMF, so that the PCF and/or SMF on the core network side can determine the status of the terminal according to the terminal status. information, making at least one of terminal policy (UE policy) decision, service policy decision of the first service, and setting network configuration.

In some possible implementations, the AMF can perform both S302 and S303. It can be understood that when executing S302, the AMF may also determine that the terminal status information of the UE needs to be reported to the PCF and/or SMF according to the locally saved service policy or network configuration of the first service. At this time, the AMF executes S303 to Provide terminal status information of the UE to the PCF and/or SMF.

In some possible implementations, before S303, the AMF needs to determine whether the PCF needs the terminal status information of the UE. If so, the AMF sends the terminal status information to the PCF. For example, if the UE's subscription information needs to include terminal status information, the AMF can provide the UE's terminal status information to the PCF. Here, the contract information is downloaded by AMF from the unified data management (UDM) functional entity.

Alternatively, the PCF can also subscribe to the AMF for the terminal status information event (ie, the first event, UE status information event). Then, in S303, after receiving the terminal status information of the UE, the AMF can query the event subscription and confirm that the PCF has subscribed to the first event; then, if the event reporting conditions are met, the AMF sends the terminal status information to the PCF. For example, the event reporting conditions may be UE status changes, various network policies of the first service and/or threshold arrivals in network configuration, power supply mode matching, immediate reporting upon receipt, periodic reporting, etc. Of course, event reporting conditions may also include other conditions, which are not specifically limited in this embodiment of the disclosure.

In some possible implementations, the above terminal status information event can also be subscribed by the PCF to another AMF (ie, the third core network functional entity). The AMF can be the AMF before UE handover or migration (relocation), or it can Described as old AMF. At this time, the AMF described in the above embodiment can be described as new AMF. Then, in S303, after the UE switches from the old AMF to the new AMF, if the event reporting conditions are met, the new AMF sends terminal status information to the PCF entity.

It should be understood that before the UE switches to AMF, the old AMF can send the context of the UE to the new AMF, so that the new AMF can obtain the events subscribed to by the PCF and continue to report the events.

In some possible implementations, still referring to Figure 3, after S303, the above method further includes:

S305: The AMF receives at least one of the generated or updated terminal policy, the service policy of the first service, and the network configuration sent by the PCF.

Here, at least one of the generated or updated terminal policy, the service policy of the first service, and the network configuration is generated or updated by the PCF according to the terminal status information of the UE.

In some possible implementations, embodiments of the present disclosure also provide an information reporting method. Figure 4 is a schematic flowchart of the implementation of the third status information reporting method in an embodiment of the present disclosure. As shown in Figure 4, in this embodiment, the information reporting method is applied to the fourth core network functional entity (such as SMF) side. The information reporting method may include S401 to S404.

S401. The fourth core network functional entity (such as SMF) receives the terminal status information sent by the AMF.

In some possible implementations, the AMF sends the terminal status information reported by the UE to the SMF. Here, the AMF may send the terminal status information to the SMF after receiving the terminal status information reported by the UE, or the AMF may respond to the SMF's request and send the previously saved terminal status information of the UE to the SMF. The AMF can also periodically send the UE's terminal status information to the SMF. Of course, the AMF may also send the terminal status information of the UE to the SMF in other situations, and this is not specifically limited in the embodiments of the present disclosure.

In one embodiment, the AMF sends the terminal status information to the SMF through the NAS parameter. That is to say, the AMF carries the terminal status information in the NAS parameter and sends it to the SMF.

In some possible implementations, based on the third triggering situation in the above embodiment, still referring to FIG. 4 , before S301, the above method may also include:

S404, the SMF sends a third request message (such as UE status information notification request) to the AMF to request the terminal status information notification message.

In some possible implementations, the above method further includes: SMF saving terminal status information for SMF to determine at least one of terminal policies of other processes associated with the first service, service policies of the first service, and network configuration, Of course, it can also be used to execute S403.

In some possible implementations, in S401, while sending the terminal status information to the SMF, the AMF may also send service indication information to the SMF to indicate the first service. It can be understood that after the SMF receives the service indicator, it can determine the first service according to the service indication information, and then perform S402.

After S401, SMF may perform at least one of S402 to S403:

S402: The SMF determines at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information.

It should be understood that after receiving the terminal status information, the SMF determines at least one of the terminal policy, the service policy of the first service, and the network configuration according to the power consumption status of the UE. Here the service policy and network configuration can be related to the UE's session. For example, the service policy may be a policy for executing session creation, that is, accepting or rejecting the creation of a PDU session for the first service of the UE.

In an embodiment, the SMF may determine the policy of the PDU session based on the terminal status information and the terminal's subscription information and/or service policy.

It should be noted that the execution processes of S402 and S202 are similar. For the implementation process of S402, please refer to the description of S202 in the embodiment of FIG. 2 and will not be described again here.

S403: SMF sends terminal status information to PCF.

Here, the terminal status information is also used by the PCF to determine at least one of the terminal policy, the service policy of the first service, and the network configuration. For example, policy decisions of XRM business or business groups, QoS authorization of XRM business data flow (service dataflow, SDF).

It is understandable that after receiving the terminal status information of the UE, the SMF can also forward the information to another core network functional entity, such as the PCF, so that the PCF on the core network side can make terminal policy decisions based on the terminal status information. At least one of a business policy decision and a network configuration setting.

In some possible implementations, SMF can perform both S402 and S403. It can be understood that when executing S402, the SMF may also determine that the terminal status information of the UE needs to be reported to the PCF according to the locally saved service policy or network configuration of the first service. At this time, the SMF executes S403 to provide the PCF with the terminal status information of the UE. terminal status information.

In some possible implementations, embodiments of the present disclosure also provide an information reporting method. Figure 5 is a schematic flowchart of the implementation of the fourth status information reporting method in an embodiment of the present disclosure. As shown in Figure 5, in this embodiment, the information reporting method is applied to the second core network functional entity (such as PCF) side. The information reporting method may include S501 to S504.

S501. The second core network functional entity (such as PCF) receives the terminal status information sent by the AMF and/or SMF.

Here, the terminal status information is used to indicate the power consumption status of the UE;

In some possible implementations, in S501, while sending terminal status information to the PCF, the AMF and/or SMF may also send service indication information to the PCF to indicate the first service. It can be understood that after the PCF receives the service indicator, it can determine the first service according to the service indication information, and then execute S502.

S502: The PCF determines at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information. For example, policy decisions of XRM business or business groups, QoS authorization of XRM business data flow (service dataflow, SDF).

In some possible implementations, in the above 502, the PCF may update at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information.

Then, after S502, the PCF may also perform S503, where the PCF sends at least one of the terminal policy, the service policy of the first service, and the network configuration to one or more of the AMF, SMF, base station, and UE.

Optionally, the AMF may first send at least one of the terminal policy, the service policy of the first service, and the network configuration to the base station, and then the base station sends it to the UE. Alternatively, the AMF sends at least one of the terminal policy, the service policy of the first service, and the network configuration to the UE through the N1 message. Of course, the PCF can also use other methods to send at least one of the terminal policy, the service policy of the first service, and the network configuration to at least one of the AMF, SMF, base station, and UE. This is not specifically limited in the embodiments of the present disclosure. .

It should be noted that at least one of the terminal policy, the service policy of the first service and the network configuration sent by the PCF are the terminal policy, the service policy of the first service and the network configuration generated or updated based on the terminal status information.

At this point, the reporting process of terminal status information has been implemented.

It should be noted that the above reporting process can be multiplexed with the UE's registration process, PDU session establishment process, connection recovery process and other processes.

In the embodiment of the present disclosure, by providing the terminal status information of the UE to the network side (including the access network side and the core network side), the network can match the service traffic characteristics and terminal energy consumption management according to the terminal status information, that is, according to the terminal status information The power consumption state implements policy decisions and execution for the first business to ensure business requirements and user experience. At the same time, the terminal status information is provided to the access network side, which also facilitates the access network side to make decisions or update at least one of the terminal policy, the service policy of the first service, and the network configuration based on the UE status information.

Based on the same inventive concept, an embodiment of the present disclosure provides a communication device. Figure 6 is a schematic structural diagram of a communication device in an embodiment of the present disclosure. Referring to Figure 6, the communication device 600 may include: a processing module 601, The receiving module 602 and the sending module 603.

In some possible implementations, the communication device can be an access network functional entity in the communication system (such as the above-mentioned base station) or a chip or system-on-chip of the access network functional entity. It can also be an access network functional entity used in the access network functional entity. Functional modules that implement the methods described in the above embodiments. The communication device can realize the functions performed by the access network functional entities in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.

Correspondingly, the receiving module 602 is configured to receive terminal status information sent by the terminal, and the terminal status information is used to represent the power consumption status of the terminal; the processing module 601 is configured to determine the terminal policy and the first service based on the terminal status information. At least one of service policy and network configuration; the sending module 603 is configured to send terminal status information to the core network functional entity. The terminal status information is also used by the core network functional entity to determine the terminal policy, the business policy of the first service, and the network At least one of the configuration.

In some possible implementations, the receiving module 602 is also configured to receive service indication information sent by the terminal, where the service indicator is used to indicate the first service.

In some possible implementations, the sending module 603 is also configured to send a first request message to the terminal, where the first request message is used to request terminal status information.

In some possible implementations, the receiving module 602 is also configured to receive a second request message sent by the core network functional entity before the sending module 603 sends the first request message to the terminal. The second request message is used to request the terminal status. Information; the sending module 603 is also configured to send the terminal status information to the core network functional entity after the receiving module 602 receives the terminal status information sent by the terminal.

In some possible implementations, the processing module 601 is also configured to determine the matching between the terminal status information and at least one of the terminal policy, the service policy of the first service, and the network configuration; and determine the corresponding terminal according to the matching. At least one of a policy, a service policy of the first service, and a network configuration.

In the present disclosure, the processing module 601 is also configured to determine whether the terminal supports the first capability according to the terminal status information. The first capability is the capability required by the first service; if the terminal supports the first capability, determine whether the first terminal supports the first capability. at least one of the policy, the first service policy of the first service and the first network configuration; if the terminal does not support the first capability, determine the second terminal policy, the second service policy of the first service and/or the second network configuration.

In some possible implementations, the processing module 601 is also configured to determine whether the terminal supports the first capability according to the terminal status information. The first capability is the capability required by the first service; if the terminal supports the first capability, determine The first terminal policy, the first service policy of the first service and the first network configuration; if the terminal does not support the first capability, determine at least one of the second terminal policy, the second service policy of the first service and the second network configuration. one.

In some possible implementations, the receiving module 602 is also configured to receive a third request message sent by the core network functional entity. The third request message is used to request a terminal status information notification message; the sending module 603 is also configured to send a request message to the core network functional entity. The network function entity sends a terminal status information notification message, and the terminal status information notification message carries terminal status information.

In some possible implementations, in response to the terminal status information being carried in the AN parameter, the sending module 603 is also configured to extract the terminal status information from the AN parameter; and carry the terminal status information in the NAS parameter and send it to the core network functional entity. .

In some possible implementations, the sending module 603 is also configured to add the terminal status information to the NAS parameters according to at least one of the terminal policy, the service policy of the first service, and the network configuration; and carry the NAS parameters in the NAS message Sent to the core network functional entity.

In some possible implementations, the processing module 601 is also configured to save terminal status information.

In some possible implementations, the first service is an XRM service.

In some possible implementations, the communication device 600 may be the first core network functional entity (such as AMF) in the communication system or a chip or system-on-chip of the first core network functional entity, or may also be the first core network functional entity. The functional modules used to implement the methods described in the above embodiments. The communication device can realize the functions performed by the first core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.

Correspondingly, the receiving module 602 is configured to receive terminal status information sent by the access network functional entity, and the terminal status information is used to represent the power consumption status of the terminal; the processing module 601 is configured to determine the terminal policy, At least one of the service policy of the first service and the network configuration; the sending module 603 is configured to send terminal status information to the second core network functional entity, and the terminal status information is also used by the second core network functional entity to determine the terminal policy, At least one of the service policy of the first service and the network configuration.

In some possible implementations, the receiving module 602 is also configured to receive service indication information sent by the access network functional entity, where the service indicator is used to indicate the first service.

In some possible implementations, the sending module 603 is also configured to send a first request message to the access network device before the receiving module 602 receives the terminal status information sent by the access network functional entity. The first request message is used to Requests terminal status information for a terminal.

In some possible implementations, the receiving module 602 is also configured to receive NAS parameters sent by the access network functional entity, where the NAS parameters carry terminal status information.

In some possible implementations, the processing module 601 is also configured to determine that the terminal's subscription information needs to include terminal status information before the sending module 603 sends the terminal status information to the second core network functional entity.

In some possible implementations, the processing module 601 is also configured to query event subscriptions and confirm the subscription to the first event associated with the terminal status information; the sending module 603 is also configured to, if the event reporting conditions are met, send the The second core network functional entity sends terminal status information.

In some possible implementations, the first event is subscribed by the second core network functional entity to the third core network functional entity; the sending module 603 is also configured to switch from the third core network functional entity to the first core network functional entity at the terminal. After the core network function entity is connected, the terminal status information is sent to the second core network function entity.

In some possible implementations, the receiving module 602 is also configured to receive at least one of the terminal policy, the service policy of the first service, and the network configuration sent by the second core network functional entity. At least one of the service policy and the network configuration is generated or updated by the second core network functional entity based on the terminal status information.

In some possible implementations, the first service is an XRM service.

In some possible implementations, the above-mentioned communication device 600 may be the fourth core network functional entity (such as SMF) in the communication system or a chip or system-on-chip of the fourth core network functional entity, or may also be the fourth core network functional entity. The functional modules used to implement the methods described in the above embodiments. The communication device can realize the functions performed by the fourth core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.

Correspondingly, the receiving module 602 is configured to receive the terminal status information sent by the first core network functional entity. The terminal status information is used to represent the power consumption status of the terminal; the processing module 601 is configured to determine the terminal policy based on the terminal status information. , at least one of the service policy of the first service and the network configuration; the sending module 603 is configured to send terminal status information to the second core network functional entity, and the terminal status information is also used by the second core network functional entity to determine the terminal policy , at least one of the service policy of the first service and the network configuration.

In some possible implementations, the receiving module 602 is further configured to receive service indication information sent by the first core network functional entity, where the service indicator is used to indicate the first service.

In some possible implementations, the processing module 601 is also configured to determine the policy of the PDU session based on the terminal status information and the terminal's subscription information and/or service policy.

In some possible implementations, the receiving module 602 is configured to receive NAS parameters sent by the first core network device, where the NAS parameters carry terminal status information.

In some possible implementations, the first service is an XRM service.

In some possible implementations, the above-mentioned communication device 600 can be a second core network functional entity (such as PCF) in the communication system or a chip or system-on-chip of the second core network functional entity. It can also be a second core network functional entity. The functional modules used to implement the methods described in the above embodiments. The communication device can realize the functions performed by the second core network functional entity in the above embodiments, and these functions can be realized by hardware executing corresponding software. These hardware or software include one or more modules corresponding to the above functions.

Correspondingly, the receiving module 602 is configured to receive terminal status information, and the terminal status information is used to represent the power consumption status of the terminal; the processing module 601 is configured to determine the terminal policy, the service policy of the first service, and At least one of the network configurations.

In some possible implementations, the receiving module 602 is configured to receive service indication information, and the service indicator is used to indicate the first service.

In some possible implementations, the receiving module 602 is also configured to receive terminal status information sent by the first core network functional entity and/or the fourth core network functional entity, the first core network functional entity being used for mobility management, The fourth core network functional entity is used for session management.

In some possible implementations, the above device also includes: a sending module 603; a processing module 601, which is also configured to update at least one of the terminal policy, the service policy of the first service, and the network configuration according to the terminal status information; sending Module 603 is configured to send at least one of the updated terminal policy, the service policy of the first service, and the network configuration to the first core network functional entity.

It should be noted that for the specific implementation process of the processing module 601, the receiving module 602 and the sending module 603, reference can be made to the detailed description of the embodiments in Figures 2 to 5. For the sake of simplicity of the description, they will not be described again here.

The receiving module 602 mentioned in the embodiment of the present disclosure may be a receiving interface, a receiving circuit or a receiver, etc.; the sending module 603 may be a sending interface, a sending circuit or a transmitter, etc.; and the processing module 601 may be one or more processors.

Based on the same inventive concept, embodiments of the present disclosure provide a communication device. The communication device may be the access network functional entity, the first core network functional entity, the second core network functional entity described in one or more of the above embodiments. Entity or fourth core network functional entity. Figure 7 is a schematic structural diagram of another communication device in an embodiment of the present disclosure. Referring to Figure 7, the communication device 700 uses general computer hardware, including a processor 701, a memory 702, a bus 703, an input device 704 and Output device 705.

In some possible implementations, memory 702 may include computer storage media in the form of volatile and/or non-volatile memory, such as read-only memory and/or random access memory. Memory 702 may store an operating system, application programs, other program modules, executable code, program data, user data, and the like.

Input device 704 may be used to enter commands and information to a communication device, such as a keyboard or pointing device such as a mouse, trackball, touch pad, microphone, joystick, game pad, satellite television dish, scanner, or similar device. These input devices may be connected to processor 701 via bus 703 .

The output device 705 can be used for communication devices to output information. In addition to the monitor, the output device 705 can also be other peripheral output devices, such as speakers and/or printing devices. These output devices can also be connected to the processor 701 through the bus 703. .

The communication device may be connected to a network through the antenna 706, such as a local area network (LAN). In a networked environment, the computer execution instructions stored in the control device can be stored in a remote storage device and are not limited to local storage.

When the processor 701 in the communication device executes the executable code or application program stored in the memory 702, the communication device executes the relay communication method on the UE side or the network device side in the above embodiments. For the specific execution process, refer to the above embodiments. , which will not be described in detail here.

In addition, the above-mentioned memory 702 stores computer execution instructions for realizing the functions of the processing module 601, the receiving module 602 and the sending module 603 in FIG. 6 . The functions/implementation processes of the processing module 601, the receiving module 602 and the sending module 603 in Figure 6 can all be implemented by the processor 701 in Figure 7 calling the computer execution instructions stored in the memory 702. For specific implementation processes and functions, please refer to the above-mentioned relevant Example.

Based on the same inventive concept, embodiments of the present disclosure provide a network functional entity, such as an access network functional entity, a first core network functional entity, a second core network functional entity or a fourth core network functional entity.

Figure 8 is a schematic structural diagram of a network functional entity in an embodiment of the present disclosure. Referring to Figure 8, the network functional entity 800 may include a processing component 801, which further includes one or more processors, and is represented by a memory 802 A memory resource used to store instructions, such as application programs, that can be executed by processing component 801. An application program stored in memory 802 may include one or more modules, each of which corresponds to a set of instructions. In addition, the processing component 801 is configured to execute instructions to perform any of the foregoing methods applied to the network device.

The network function entity 800 may also include a power supply component 803 configured to perform power management of the network function entity 800, a wired or wireless network interface 804 configured to connect the network function entity 800 to the network, and an input/output (I/O ) interface 805. The network function entity 800 may operate based on an operating system stored in the memory 802, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™ or the like.

Based on the same inventive concept, an embodiment of the present disclosure also provides a communication device, such as an access network functional entity, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer-executable instructions stored in the memory. , to implement the information reporting method on the access network function entity side as described in one or more of the above embodiments.

Based on the same inventive concept, an embodiment of the present disclosure also provides a communication device, such as a first core network functional entity, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer executable data stored on the memory. instructions to implement the information reporting method on the first core network functional entity side as described in one or more of the above embodiments.

Based on the same inventive concept, an embodiment of the present disclosure also provides a communication device, such as a fourth core network functional entity, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer executable data stored on the memory. instructions to implement the information reporting method on the fourth core network functional entity side as described in one or more of the above embodiments.

Based on the same inventive concept, an embodiment of the present disclosure also provides a communication device, such as a second core network functional entity, including: a memory and a processor; the processor is connected to the memory and is configured to execute computer executable data stored on the memory. instructions to implement the information reporting method on the second core network functional entity side as described in one or more of the above embodiments.

Based on the same inventive concept, embodiments of the present disclosure also provide a computer-readable storage medium. Instructions are stored in the computer-readable storage medium; when the instructions are run on the computer, they are used to execute the network in one or more of the above embodiments. Information reporting method on the functional entity side. Here, the network functional entity may include: an access network functional entity, a first core network functional entity, a second core network functional entity or a fourth core network functional entity.

Based on the same inventive concept, embodiments of the present disclosure also provide a computer program or computer program product. When the computer program product is executed on a computer, it causes the computer to implement the information on the entity side of the network function in one or more of the above embodiments. Reporting method. Here, the network functional entity may include: an access network functional entity, a first core network functional entity, a second core network functional entity or a fourth core network functional entity.

Other embodiments of the invention will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common common sense or customary technical means in the technical field that are not disclosed in the present disclosure. . It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.

It is to be understood that the present invention is not limited to the precise construction described above and illustrated in the accompanying drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the invention is limited only by the appended claims.

Claims

An information reporting method, wherein the method includes:

The access network functional entity receives terminal status information sent by the terminal, where the terminal status information is used to represent the power consumption status of the terminal;

The access network functional entity performs at least one of the following:

Determine at least one of a terminal policy, a service policy of the first service, and a network configuration according to the terminal status information;

The terminal status information is sent to the core network functional entity, and the terminal status information is also used by the core network functional entity to determine at least one of a terminal policy, a service policy of the first service, and a network configuration.
The method according to claim 1, wherein the core network functional entity includes at least one of the following:

Mobility management function entity AMF;

Session management function entity SMF;

Policy control function entity PCF.
The method of claim 1, further comprising:

The access network functional entity receives the service indication information sent by the terminal, and the service indicator is used to indicate the first service.
The method according to claim 3, wherein the terminal status information includes at least one of the following:

battery power;

Battery Life;

Power supply mode;

Terminal overheating status.
The method according to claim 1, wherein the access network functional entity configures one of the network configurations for a public land mobile network PLMN.
The method of claim 1, further comprising:

The access network functional entity sends a first request message to the terminal, where the first request message is used to request the terminal status information.
The method according to claim 6, wherein before the access network functional entity sends the first request message to the terminal, the method further includes:

The access network functional entity receives a second request message sent by the core network functional entity, where the second request message is used to request the terminal status information;

After the access network functional entity receives the terminal status information sent by the terminal, the method further includes:

The access network functional entity sends the terminal status information to the core network functional entity.
The method according to claim 1, wherein the access network functional entity determines at least one of a terminal policy, a service policy of the first service and a network configuration according to the terminal status information, including:

The access network functional entity determines a match between the terminal status information and at least one of a terminal policy, a service policy of the first service, and a network configuration;

The access network functional entity determines at least one of the corresponding terminal policy, the service policy of the first service, and the network configuration according to the matching situation.
The method according to claim 1, wherein the access network functional entity determines at least one of a terminal policy, a service policy of the first service and a network configuration according to the terminal status information, including:

The access network functional entity determines whether the terminal supports a first capability based on the terminal status information, where the first capability is a capability required by the first service;

If the terminal supports the first capability, the access network functional entity determines at least one of a first terminal policy, a first service policy of the first service, and a first network configuration;

If the terminal does not support the first capability, the access network functional entity determines at least one of a second terminal policy, a second service policy of the first service, and a second network configuration.
The method according to claim 1, wherein the terminal status information is carried in a first Radio Resource Control (RRC) message, and the first RRC message is used to trigger the terminal to switch from an inactive state to a connected state.
The method of claim 10, wherein the method further includes:

The access network functional entity receives a third request message sent by the core network functional entity, and the third request message is used to request the terminal status information notification message;

The access network functional entity sends the terminal status information notification message to the core network functional entity, and the terminal status information notification message carries the terminal status information.
The method according to claim 1, wherein the terminal status information is carried in an access network AN parameter; or, the terminal status information is carried in an AN parameter and a non-access layer NAS parameter.
The method according to claim 12, wherein in response to the terminal status information being carried in an AN parameter, the access network functional entity sends the terminal status information to the core network functional entity, including:

The access network functional entity extracts the terminal status information from the AN parameters;

The access network functional entity carries the terminal status information in the NAS parameter and sends it to the core network functional entity.
The method according to claim 13, wherein the access network functional entity carries the terminal status information in the NAS parameter and sends it to the core network functional entity, including:

The access network functional entity adds the terminal status information to the NAS parameter according to at least one of a terminal policy, a service policy of the first service, and a network configuration;

The access network functional entity carries the NAS parameter in a NAS message and sends it to the core network functional entity.
The method according to any one of claims 12 to 14, wherein in response to the terminal status information being carried in an AN parameter and a non-access layer NAS parameter, the AN parameter and the NAS parameter are carried in a packet data unit (PDU) messages during the session establishment process; and/or, the AN parameter and the NAS parameter are carried in messages during the registration process.
The method of claim 1, further comprising:

The access network functional entity stores the terminal status information.
The method according to claim 1, wherein the first service is an extended reality and media XRM service.
An information reporting method, wherein the method includes:

The first core network functional entity receives terminal status information sent by the access network functional entity, where the terminal status information is used to represent the power consumption status of the terminal;

The first core network functional entity performs at least one of the following:

Determine at least one of a terminal policy, a service policy of the first service, and a network configuration according to the terminal status information;

Send the terminal status information to the second core network functional entity, and the terminal status information is also used by the second core network functional entity and/or the fourth core network functional entity to determine the terminal policy, the service policy of the first service, and At least one of the network configurations.
The method of claim 18, wherein the method further includes:

The first core network functional entity receives the service indication information sent by the access network functional entity, and the service indicator is used to indicate the first service.
The method according to claim 19, wherein the terminal status information includes at least one of the following:

battery power;

Battery Life;

Power supply mode;

Terminal overheating status.
The method according to claim 18, wherein before the first core network functional entity receives the terminal status information sent by the access network functional entity, the method further includes:

The first core network functional entity sends a first request message to the access network device, where the first request message is used to request terminal status information of the terminal.
The method according to claim 18, wherein the first core network functional entity receives the terminal status information sent by the access network functional entity, including:

The first core network functional entity receives the non-access layer NAS parameters sent by the access network functional entity, where the NAS parameters carry the terminal status information.
The method according to claim 18, wherein before the first core network functional entity sends the terminal status information to the second core network functional entity, the method further includes:

The first core network functional entity determines that the subscription information of the terminal needs to include the terminal status information.
The method according to claim 18, wherein the first core network functional entity sends the terminal status information to the second core network functional entity, including:

The first core network functional entity queries the event subscription and confirms the subscription to the first event associated with the terminal status information;

When event reporting conditions are met, the first core network functional entity sends the terminal status information to the second core network functional entity.
The method according to claim 24, wherein the first event is subscribed by the second core network functional entity.
The method according to claim 24, wherein the first event is subscribed by the second core network functional entity to a third core network functional entity;

The first core network functional entity sends the terminal status information to the second core network functional entity, including:

After the terminal is switched from the third core network functional entity to the first core network functional entity, the first core network functional entity sends the terminal status information to the second core network functional entity.
The method of claim 24, wherein the method further includes:

The first core network functional entity receives at least one of the terminal policy, the service policy of the first service and the network configuration sent by the second core network functional entity, the terminal policy, the service policy of the first service and the network configuration. At least one of the configurations is generated or updated by the second core network functional entity according to the terminal status information.
The method of claim 18, wherein the method further includes:

The first core network functional entity stores the terminal status information.
The method according to claim 18, wherein the first service is an extended reality and media XRM service.
An information reporting method, wherein the method includes:

The fourth core network functional entity receives the terminal status information sent by the first core network functional entity, where the terminal status information is used to represent the power consumption status of the terminal;

The fourth core network functional entity performs at least one of the following:

Determine at least one of a terminal policy, a service policy of the first service, and a network configuration according to the terminal status information;

The terminal status information is sent to the second core network functional entity, and the terminal status information is also used by the second core network functional entity to determine at least one of the terminal policy, the service policy of the first service, and the network configuration.
The method of claim 30, wherein the method further includes:

The fourth core network functional entity receives the service indication information sent by the first core network functional entity, and the service indicator is used to indicate the first service.
The method according to claim 30, wherein the terminal status information includes at least one of the following:

battery power;

Battery Life;

Power supply mode;

Terminal overheating status.
The method according to claim 30, wherein the fourth core network functional entity determines at least one of a terminal policy, a service policy of the first service and a network configuration according to the terminal status information, including:

The fourth core network functional entity determines the policy of the PDU session based on the terminal status information and the subscription information and/or service policy of the terminal.
The method according to claim 30, wherein the fourth core network functional entity receives the terminal status information sent by the first core network functional entity, including:

The fourth core network functional entity receives the non-access layer NAS parameters sent by the first core network device, where the NAS parameters carry the terminal status information.
The method of claim 30, wherein the method further includes:

The fourth core network functional entity stores the terminal status information.
The method of claim 30, wherein the first service is an extended reality and media XRM service.
An information reporting method, wherein the method includes:

The second core network functional entity receives terminal status information, where the terminal status information is used to represent the power consumption status of the terminal;

The second core network functional entity determines at least one of a terminal policy, a service policy of the first service, and a network configuration based on the terminal status information.
The method of claim 37, wherein the method further includes:

The second core network functional entity receives service indication information, and the service indicator is used to indicate the first service.
The method according to claim 37, wherein the terminal status information includes at least one of the following:

battery power;

Battery Life;

Power supply mode;

Terminal overheating status.
The method according to claim 37, wherein the second core network functional entity receives terminal status information, including:

The second core network functional entity receives the terminal status information sent by the first core network functional entity and/or the fourth core network functional entity. The first core network functional entity is used for mobility management. The fourth core network functional entity Core network functional entities are used for session management.
The method of claim 37, wherein the method further includes:

The second core network functional entity generates or updates at least one of a terminal policy, a service policy of the first service, and a network configuration according to the terminal status information;

The second core network functional entity sends the generated or updated terminal policy and the service of the first service to one or more of the first core network functional entity, the fourth core network functional entity, the access network functional entity and the terminal. At least one of the policy and network configuration.