WO2023164849A1 - 无线通信方法、装置、设备、存储介质及程序产品 - Google Patents

无线通信方法、装置、设备、存储介质及程序产品 Download PDF

Info

Publication number
WO2023164849A1
WO2023164849A1 PCT/CN2022/078902 CN2022078902W WO2023164849A1 WO 2023164849 A1 WO2023164849 A1 WO 2023164849A1 CN 2022078902 W CN2022078902 W CN 2022078902W WO 2023164849 A1 WO2023164849 A1 WO 2023164849A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
terminal device
message
policy
rule
Prior art date
Application number
PCT/CN2022/078902
Other languages
English (en)
French (fr)
Other versions
WO2023164849A9 (zh
Inventor
许阳
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2022/078902 priority Critical patent/WO2023164849A1/zh
Publication of WO2023164849A1 publication Critical patent/WO2023164849A1/zh
Publication of WO2023164849A9 publication Critical patent/WO2023164849A9/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a wireless communication method, device, equipment, storage medium, and program product.
  • the core network can provide some policy rules (such as URSP (UE Route Selection Policy, UE routing selection policy), ANDSP (Access Network Discovery & Selection Policy, access network discovery and selection policy) etc.) to terminal equipment for terminal equipment and network side able to communicate.
  • URSP UE Route Selection Policy, UE routing selection policy
  • ANDSP Access Network Discovery & Selection Policy, access network discovery and selection policy
  • Embodiments of the present application provide a wireless communication method, device, equipment, storage medium, and program product. Described technical scheme is as follows:
  • a wireless communication method includes:
  • the terminal device sends first information to a network element of the core network, where the first information includes information related to usage of policy rules configured by the terminal device for the core network.
  • a wireless communication method includes:
  • the network element of the core network receives the first information from the terminal device, where the first information includes information related to usage of policy rules configured by the terminal device for the core network.
  • a wireless communication device includes:
  • a sending module configured to send first information to a network element of the core network, where the first information includes information related to usage of policy rules configured by the terminal device for the core network.
  • a wireless communication device includes:
  • the receiving module is configured to receive first information from the terminal device, where the first information includes information related to usage of policy rules configured by the terminal device for the core network.
  • a communication device includes a processor and a memory, a computer program is stored in the memory, and the processor executes the computer program to realize the terminal device side A wireless communication method, or a wireless communication method on the network element side of the core network.
  • a computer-readable storage medium is provided, and a computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by a processor to realize the above-mentioned wireless communication on the side of the terminal device.
  • a chip is provided, the chip includes a programmable logic circuit and/or program instructions, and when the chip is running, it is used to implement the above-mentioned wireless communication method on the terminal device side, or the above-mentioned A wireless communication method on the network element side of the core network.
  • a computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and a processor reads from the The computer-readable storage medium reads and executes the computer instructions, so as to implement the above-mentioned wireless communication method on the terminal device side, or the above-mentioned wireless communication method on the network element side of the core network.
  • the first information includes information related to the use of policy rules configured by the terminal device for the core network, so that the network element of the core network can know the use of the policy rules by the terminal device, It facilitates the configuration and update of subsequent policy rules and helps to improve communication reliability.
  • FIG. 1 is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • FIG. 2 is an architecture diagram of a 5G system provided by an embodiment of the present application.
  • FIG. 3 is an architecture diagram of a 5G system provided by another embodiment of the present application.
  • Fig. 4 is a flow chart of UE (User Equipment, user equipment) policy configuration provided by an embodiment of the present application;
  • Fig. 5 is a flowchart of message interaction between PCF (Policy Control Function, policy control function) and UE provided by an embodiment of the present application;
  • PCF Policy Control Function, policy control function
  • FIG. 6 is a flow chart of message interaction between the PCF and the UE provided by another embodiment of the present application.
  • Fig. 7 is a schematic diagram of an application data flow provided by an embodiment of the present application bound to a PDU (Packet Data Unit, packet data unit) session according to URSP;
  • PDU Packet Data Unit, packet data unit
  • FIG. 8 is a flowchart of PDU session establishment rejection and retry provided by an embodiment of the present application.
  • FIG. 9 is a flowchart of a wireless communication method provided by an embodiment of the present application.
  • FIG. 10 is a flowchart of a wireless communication method provided by another embodiment of the present application.
  • FIG. 11 to FIG. 15 are schematic diagrams of the format of the reply message corresponding to the UCU message provided by one embodiment of the present application.
  • FIG. 16 is a schematic diagram of the format of a reply message corresponding to a UCU message provided by another embodiment of the present application.
  • FIG. 17 is a flowchart of a wireless communication method provided by another embodiment of the present application.
  • FIG. 18 is a flowchart of a UE sending a registration request message to a core network element provided by an embodiment of the present application
  • FIG. 19 is a flowchart of a wireless communication method provided by another embodiment of the present application.
  • Fig. 20 is a block diagram of a wireless communication device provided by another embodiment of the present application.
  • Fig. 21 is a block diagram of a wireless communication device provided by another embodiment of the present application.
  • Fig. 22 is a schematic structural diagram of a terminal device provided by an embodiment of the present application.
  • Fig. 23 is a schematic structural diagram of a network device provided by an embodiment of the present application.
  • the network architecture and business scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the evolution of the technology and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.
  • the technical solution of the embodiment of the present application can be applied to various communication systems, such as: Global System of Mobile communication (Global System of Mobile communication, GSM) system, code division multiple access (Code Division Multiple Access, CDMA) system, broadband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced long term evolution (LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) on unlicensed spectrum unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunications System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.
  • GSM Global System of Mobile
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • V2X Vehicle to everything
  • the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, may also be applied to a dual connectivity (Dual Connectivity, DC) scenario, and may also be applied to an independent (Standalone, SA) network deployment scenario.
  • Carrier Aggregation, CA Carrier Aggregation
  • DC Dual Connectivity
  • SA independent network deployment scenario
  • the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to a licensed spectrum, wherein the licensed spectrum can also be Considered as unshared spectrum.
  • Non-Terrestrial Networks NTN
  • TN terrestrial communication network
  • FIG. 1 shows a schematic diagram of a network architecture provided by an embodiment of the present application.
  • the network architecture may include: a terminal device 10 , an access network device 20 and a core network element 30 .
  • a terminal device 10 may refer to a UE, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user device.
  • the terminal device 10 can also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol, session initiation protocol) phone, a WLL (Wireless Local Loop, wireless local loop) station, a PDA (Personal Digital Assistant, personal digital Processing), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5GS (5th Generation System, fifth-generation mobile communication system) or future evolution
  • the terminal equipment and the like in the PLMN Public Land Mobile Network, public land mobile communication network
  • the embodiment of the present application is not limited to this.
  • the devices mentioned above are collectively referred to as terminal devices.
  • terminal devices 10 The number of terminal devices 10 is generally multiple, and one or more terminal devices 10 may be distributed in a cell managed by each access network device 20 .
  • terminal device and “UE” are usually used interchangeably, but those skilled in the art can understand their meanings.
  • the access network device 20 is a device deployed in an access network to provide a wireless communication function for the terminal device 10 .
  • the access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, and so on.
  • the names of devices with access network device functions may be different. For example, in 5G NR systems, they are called gNodeB or gNB. With the evolution of communication technology, the name "access network equipment" may change.
  • access network devices For the convenience of description, in the embodiment of the present application, the above-mentioned devices that provide the wireless communication function for the terminal device 10 are collectively referred to as access network devices.
  • a communication relationship can be established between the terminal device 10 and the core network element 30 through the access network device 20 .
  • the access network device 20 may be one or more eNodeBs in EUTRAN (Evolved Universal Terrestrial Radio Access Network, Evolved Universal Terrestrial Radio Network) or EUTRAN;
  • EUTRAN Evolved Universal Terrestrial Radio Access Network
  • EUTRAN EUTRAN
  • the access network device 20 may be a RAN (Radio Access Network, radio access network) or one or more gNBs in the RAN.
  • the core network element 30 is a network element deployed in the core network.
  • the functions of the core network element 30 are mainly to provide user connections, manage users, and carry out services, and provide an interface to the external network as a bearer network.
  • the core network elements in the 5G NR system can include AMF (Access and Mobility Management Function, access and mobility management function), UPF (User Plane Function, user plane function) and SMF (Session Management Function, session management function) ) and other network elements.
  • AMF Access and Mobility Management Function, access and mobility management function
  • UPF User Plane Function, user plane function
  • SMF Session Management Function, session management function
  • core network elements can be regarded as functional entities, and one or more core network elements can be deployed on one physical device.
  • the access network device 20 and the core network element 30 communicate with each other through a certain air interface technology, such as the NG interface in the 5G NR system.
  • the access network device 20 and the terminal device 10 communicate with each other through a certain air interface technology, such as a Uu interface.
  • the "5G NR system" in the embodiment of the present application may also be called a 5G system or an NR system, but those skilled in the art can understand its meaning.
  • the technical solutions described in the embodiments of this application can be applied to LTE systems, 5G NR systems, and subsequent evolution systems of 5G NR systems, and can also be applied to systems such as NB-IoT (Narrow Band Internet of Things, narrowband Internet of Things) system and other communication systems, this application is not limited to this.
  • NB-IoT Near Band Internet of Things, narrowband Internet of Things
  • the access network device may provide services for the cell, and the terminal device communicates with the access network device through the transmission resources (for example, frequency domain resources, or spectrum resources) on the carrier used by the cell
  • the cell may be a cell corresponding to an access network device (such as a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell.
  • the small cell here may include: a metro cell, a micro cell Micro cell, Pico cell, Femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • FIG. 2 shows a schematic diagram of a system architecture of a 5GS (5th Generation System, fifth-generation mobile communication system) provided by an embodiment of the present application.
  • the system architecture 200 may include: UE (that is, the "terminal device” introduced above), (R)AN ((Radio) Access Network, (wireless) access network), Core (core network ) and DN (Data Network, data network).
  • UE, (R)AN, and Core are the main components of the architecture. Logically, they can be divided into two parts: the user plane and the control plane.
  • the control plane is responsible for the management of the mobile network
  • the user plane is responsible for the transmission of service data.
  • the NG2 reference point is located between the (R)AN control plane and the Core control plane
  • the NG3 reference point is located between the (R)AN user plane and the Core user plane
  • the NG6 reference point is located between the Core user plane and the data network.
  • the UE It is the entrance for mobile users to interact with the network. It can provide basic computing capabilities and storage capabilities, display service windows to users, and receive user operation inputs. The UE will adopt the next-generation air interface technology to establish a signal connection and a data connection with the (R)AN, thereby transmitting control signals and service data to the mobile network.
  • (R)AN Similar to the base station in the traditional network, it is deployed close to the UE, provides network access functions for authorized users in a specific area, and can use transmission tunnels of different qualities to transmit user data according to user levels and service requirements. . (R)AN can manage its own resources, use them reasonably, provide access services for UEs on demand, and forward control signals and user data between UEs and the core network.
  • Core responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing functions such as session management, mobility management, policy management, and security authentication for the UE.
  • the UE When the UE is attached, it provides network access authentication for the UE; when the UE has a service request, it allocates network resources for the UE; when the UE moves, it updates the network resources for the UE; when the UE is idle, it provides a quick recovery mechanism for the UE:
  • the UE When the UE is deattached, it releases network resources for the UE; when the UE has business data, it provides data routing functions for the UE, such as forwarding uplink data to the DN; or receiving UE downlink data from the DN and forwarding it to the (R)AN, thereby sent to the UE.
  • the DN It is a data network that provides business services for users.
  • the client is located in the UE, and the server is located in the data network.
  • the data network can be a private network, such as a local area network, or an external network that is not controlled by the operator, such as the Internet, or a proprietary network jointly deployed by the operator, such as for configuring IMS (IP Multimedia Core Network Subsystem, IP Multimedia Network Subsystem) service.
  • IMS IP Multimedia Core Network Subsystem, IP Multimedia Network Subsystem
  • Figure 3 is the detailed architecture determined on the basis of Figure 2, where the core network user plane includes UPF (User Plane Function, user plane function); the core network control plane includes AUSF (Authentication Server Function, authentication server function), AMF, SMF , NSSF (Network Slice Selection Function, network slice selection function), NEF (Network Exposure Function, network open function), NRF (Network Repository Function, network storage function), UDM (Unified Data Management, unified data management), PCF, AF (Application Function, application function).
  • UPF User Plane Function, user plane function
  • the core network control plane includes AUSF (Authentication Server Function, authentication server function), AMF, SMF , NSSF (Network Slice Selection Function, network slice selection function), NEF (Network Exposure Function, network open function), NRF (Network Repository Function, network storage function), UDM (Unified Data Management, unified data management), PCF, AF (Application Function, application function).
  • the UE performs AS (Access Stratum, access layer) connection with (R) AN through the Uu interface, exchanges AS messages and wireless data transmission, and the UE performs NAS (Non Access Stratum, Non Access Stratum, non-access stratum) to connect and exchange NAS messages.
  • AMF is the mobility management function in the core network
  • SMF is the session management function in the core network.
  • the AMF is also responsible for forwarding session management related messages between the UE and the SMF.
  • the PCF is a policy management function in the core network, and is responsible for formulating policies related to UE mobility management, session management, and charging.
  • UPF is the user plane function in the core network, and performs data transmission with the external data network through the N6 interface, and performs data transmission with the (R)AN through the N3 interface.
  • the names of the interfaces between network elements in FIG. 2 and FIG. 3 are just examples, and the names of the interfaces in specific implementations may be other names, which are not specifically limited in this embodiment of the present application.
  • the names of network elements (such as SMF, AF, UPF, etc.) included in FIG. 2 and FIG. 3 are only examples, and do not limit the functions of the network elements themselves. In 5GS and other future networks, the above-mentioned network elements may also have other names, which are not specifically limited in this embodiment of the present application.
  • some or all of the above-mentioned network elements may use the terms in 5G, or may use other names, etc., which will be described in a unified manner here, and will not be described in detail below.
  • the name of the message (or signaling) transmitted between the above network elements is only an example, and does not constitute any limitation on the function of the message itself.
  • the policy-related network elements are mainly PCF, AMF, SMF, RAN, and UE.
  • SMF is mainly responsible for the execution of policies related to sessions
  • AMF is mainly responsible for the execution of policies related to access and UE policies.
  • the policy delivery and update on the two network elements (AMF and SMF) are all controlled by PCF.
  • the PCF and the UE monitor the information related to the UE policy through the Container (container), including the content of the UE policy, the UE policy identifier, and so on.
  • the above-mentioned Container is sent by the UE to the AMF through the NAS message in the uplink direction, and the AMF continues to send (without perception or modification) to the PCF.
  • the message is sent to the UE.
  • FIG. 4 exemplarily shows a flow chart of UE policy configuration.
  • the configuration or update of UE policy is realized through the UCU (UE Configuration Update, UE configuration update) process defined by 3GPP (3rd Generation Partnership Project, third generation partnership project).
  • the UE policy configuration process is as follows:
  • PCF decides to update UE policy (PCF decides to update UE policy);
  • Namf_Communication_N1N2Message Transfer (call the message transfer service of AMF, and send the message for UE policy update to UE);
  • PCF puts the policy to be updated in a container (container) and sends it to AMF, and AMF uses NAS message to forward (eg send) to UE.
  • the reason value of "UE policy container (UE policy container)" is introduced in the downlink NAS and uplink NAS messages, that is, the reason value of "UE policy container” is increased through the Payload Container (payload container).
  • AMF sees the reason value in the Payload Container and executes the sending function.
  • This "UE policy container” is used to carry messages between PCF and UE, as shown in Figure 5 below:
  • UE STATE INDICATION UE sends UE state indication message to PCF
  • UE can also actively send UE state indication message to PCF to tell PCF the relevant state information of the UE.
  • UE policies include URSP policies, ANDSP policies, etc. URSP policies determine the binding relationship between application data and PDU sessions, and also determine what PDU sessions the UE needs to establish to satisfy this binding relationship.
  • FIG. 7 exemplarily shows a schematic diagram of binding an application data flow to a PDU session according to a URSP policy (or called a URSP rule).
  • each PDU session corresponds to a set of attribute parameters of the PDU session.
  • different application data flows are bound to different PDU sessions according to URSP rules.
  • different application data streams can also be bound to the same PDU session according to URSP rules, which is not limited here.
  • each PDU session has a corresponding attribute parameter
  • the attribute parameter includes but is not limited to at least one of the following: S-NSSAI (Single-Network Slice Selection Assistance Information, single network slice selection assistance information), DNN ( Data Network Name, data network name), PDU Session Type (PDU session type), SSC Mode (Service and Session Continuity Mode, service and session continuity mode).
  • the UE when the UE initiates a PDU session establishment request, it carries the above attribute parameters.
  • some parameters are not carried, and the corresponding attribute parameters are filled by the network side device.
  • the UE and the network side save the attribute parameters carried in the successfully established PDU session, including the attribute parameters carried in the PDU session establishment request sent by the UE and the attribute parameters filled by the network side.
  • Table 1 shows a list of traffic descriptors (Traffic Descriptor) and corresponding RSD (Route Selection Descriptor, routing selection descriptor) in the URSP rule.
  • Table 2 shows specific parameters in RSD.
  • the service descriptor in the URSP rule is used to describe a specific service, such as the application data flow shown in FIG. 7 .
  • the microblog service is described by the range of IP@1 ⁇ 9
  • the IMS (IP Multimedia Subsystem, IP Multimedia Subsystem) service is described by IMS DNN.
  • the value of S-NSSAI in the RSD and the value of the DNN are one or more, and the other parameter values in the RSD only contain one value.
  • each RSD can correspond to one or more parameter combinations, and each parameter combination is called a feature of a PDU session, and the service data corresponding to the service descriptor can be transmitted in the PDU session corresponding to a certain parameter combination of the RSD.
  • the UE can select a parameter combination according to the Component (combination) value of the corresponding RSD, and initiate a PDU session establishment request.
  • each time the UE initiates a PDU session establishment request it carries a set of session data parameters in the request message, which is a combination of parameter values in the RSD table in a certain URSP rule.
  • the UE associates the application data flow with the corresponding PDU session for transmission based on the URSP rule, and the mechanism is as follows:
  • the UE uses the USEP rule in the URSP policy to check whether the characteristics of the application data match the Traffic Descriptor (service descriptor) of a rule in the URSP rule, and the order of checking is in accordance with the URSP rule.
  • Table 1 Rule Precedence Rule priority
  • the UE checks the matching situation in sequence based on the priority order, and when a URSP rule is matched, it uses the RSD list under the URSP rule to bind the PDU session.
  • the UE When a URSP rule is matched, the UE first checks whether the currently established PDU session has valid RSD parameters that meet the matching URSP rule, and if so, binds the matching application data to the PDU session for transmission . Otherwise, try to establish a PDU session according to the Precedence (priority) order in the effective RSD.
  • the RSD parameters with higher priority are used first to establish a PDU session. If a parameter in the RSD is one or more values, the UE choose one of them and combine it with other parameters to establish a PDU session.
  • the UE will bind the application data to the session for transmission; if the session is not established successfully, the UE will try again based on other parameter combinations in the RSD or using the parameter combination in the RSD with a lower priority
  • the PDU session is established.
  • the UE checks whether the Traffic Descriptor (service descriptor) in the second-priority URSP rule can match according to the priority order
  • the application stream signature when matched, repeats the previously described process.
  • evaluation that is, finding or establishing a suitable PDU session binding.
  • the RSD in the URSP rule used by the UE is considered to be a valid RSD only if the following conditions are met to perform the above evaluation (evaluation) process:
  • the S-NSSAI must belong to one of Allowed NSSAI (non-roaming) or Mapping of Allowed NSSAI (roaming);
  • LADN Local Area Data Network, local data network
  • ATSSS Access Traffic Steering, Switching, Splitting, access traffic steering, conversion, Split
  • the UE will not use the RSD to bind data streams or establish a PDU session.
  • evaluation evaluation
  • the UE after the UE initiates the establishment of the PDU session and is rejected, it can apply for the establishment of the PDU session again according to the RSD parameter.
  • FIG. 8 it exemplarily shows a flow chart of PDU session establishment rejection and retry.
  • the UE sends a PDU session establishment request to the SMF.
  • the UE carries PDU session parameters in the PDU session establishment request message.
  • the PDU session parameters include one or more of the following: DNN, S-NSSAI, PDU Session Type, SSC Mode, PDU Session ID.
  • the SMF sends a PDU session establishment request reply (denial cause value) to the UE.
  • the SMF sends a PDU session establishment request reply to the UE. If the SMF rejects the PDU session establishment request, the PDU session establishment request reply shall include the value of the reason for rejection.
  • the UE adjusts the applied PDU session parameters according to the parameters of the URSP rule, and tries to establish the PDU session again.
  • the UE can re-initiate the PDU session establishment according to the RSD parameter adjustment parameter combination of the URSP rule.
  • the current URSP mechanism has the following problems:
  • the parameters in the URSP rules may not be recognized by the terminal device.
  • the reason is, for example, that some parameters require cooperation between operators and terminal companies, and cannot be determined unilaterally by operators.
  • the current evaluation (evaluation) rule stipulates that if the terminal device cannot recognize the parameters in a URSP rule, it will automatically ignore the URSP rule. However, the terminal device will not inform the network side which URSP rules or RSDs are ignored.
  • the terminal device When the terminal device receives the new URSP rule, the terminal device will reevaluate (evaluate) the URSP rule, and determine the new binding relationship between the application data flow and the PDU session according to the new URSP rule. However, when the terminal device evaluates the new rule and when to execute the new binding relationship, these two points are self-realized by the terminal device.
  • the evaluation (evaluation) rule will finally select a PDU session corresponding to the RSD under the URSP rule for data transmission. Then, this binding relationship will not be changed for a considerable period of time in the future.
  • the URSP rule and RSD used by the terminal device for a specific application data flow may not have the highest priority, but the network side cannot determine which URSP rule and RSD the terminal device uses for the application.
  • the terminal device itself knows the status information of the current UE policy (especially the URSP policy), and the network side cannot know it. It is not sure whether the parameters delivered to the terminal device are used or executed as expected. Therefore, a mechanism is needed for the network side to judge that the terminal device is executing UE policy rules.
  • the terminal device sends the first information to the network element of the core network, the first information includes information related to the use of the policy rules configured by the terminal device for the core network, so that the network side device can know the use of UE policies by the terminal device In this case, it is convenient for subsequent UE policy arrangement and UE policy update, which helps to improve communication reliability.
  • FIG. 9 shows a flowchart of a wireless communication method provided by an embodiment of the present application.
  • the method can be applied to the network architectures shown in FIG. 1 to FIG. 3 .
  • the method may include the steps of:
  • Step 910 the terminal device sends first information to a network element of the core network, where the first information includes information related to the use of the policy rule by the terminal device.
  • the network element of the core network receives the first information from the terminal device.
  • policy rules are configured by the core network.
  • the first information includes information related to usage of policy rules configured by the terminal device for the core network.
  • a policy rule refers to a policy or rule configured for a terminal device by an operator or other manufacturers to instruct the terminal device to perform related communication behaviors.
  • the policy rules in this application may also be called other names such as UE policies or UE rules, which are not limited in this application.
  • the policy rules include but are not limited to at least one of the following: URSP, V2XP (Vehicle to Everything Policy, vehicle networking policy), ProSeP (Proximity Service Policy, proximity service policy), ANDSP.
  • the usage of the policy rules by the terminal device refers to whether the terminal device recognizes (recognizes) certain or certain policy rules.
  • the first information is used to indicate policy rules recognized and/or not recognized by the terminal device. It should be noted that the above identification/non-identification can also be understood as identifying/disapproving, or supporting/not supporting, or using/not using in some scenarios, which is not limited in this application.
  • the aforementioned policy rules may be configured by the core network, for example, the aforementioned policy rules are configured by the network element PCF of the core network.
  • the terminal device sends first information to the PCF, where the first information includes information about the use of policy rules configured by the terminal device for the PCF.
  • the terminal device sends the first information to the PCF, which may be that the terminal device first sends the first information to the AMF, and the AMF continues to send the first information to the PCF.
  • the AMF does not perceive the first information, and sends it directly to the PCF.
  • the AMF directly sends the first information to the PCF without modifying the first information.
  • the first information includes but is not limited to at least one of the following:
  • the first sub-information is used to indicate identified and/or unidentified policy rules
  • the second sub-information is used to indicate the policy rule used to establish the PDU session
  • the third sub-information is used to indicate policy rules used for one or more applications.
  • the fourth sub-information is used to indicate the PDU session and/or network slice used for one or more applications
  • the fifth sub-information is used to indicate whether the terminal device has used the updated policy rule and/or the policy rule used by the terminal device.
  • the first sub-information is used to indicate identified policy rules, such as indicating that one or more policy rules are identified.
  • the first sub-information may include first indication information used to indicate identification.
  • the first sub-information may include identification information of at least one identified policy rule.
  • the first sub-information is used to indicate unrecognized policy rules, such as indicating that one or more policy rules are not recognized.
  • the first sub-information may include second indication information used to indicate unidentified.
  • the first sub-information may include identification information of at least one unidentified policy rule.
  • the first sub-information is used to indicate identified and unidentified policy rules, such as indicating that one or more policy rules are identified and one or more policy rules are not identified.
  • the first sub-information may include first indication information used to indicate identification, and identification information of at least one identified policy rule corresponding to the first indication information, and the first sub-information may also include The second indication information, and identification information of at least one unidentified policy rule corresponding to the second indication information.
  • the second sub-information is used to indicate policy rules used to establish one or more PDU sessions.
  • the second sub-information may include a mapping relationship between at least one set of PDU session identification information and policy rule identification information, and each set of mapping relationships is used to indicate the policy rule used to establish a certain PDU session .
  • the second sub-information may include identification information of at least one policy rule, but does not include identification information of a PDU session, and the network element of the core network determines that one or more PDU sessions are Created using the policy rule corresponding to the identification information.
  • One or more of the above PDU sessions can default to the last established PDU session, or a PDU session currently transmitting data streams, or a PDU session currently waiting to transmit data streams, or a PDU used by a certain agreed service or data stream Conversations and the like are not limited in this application.
  • the second sub-information may include identification information of at least one PDU session, but does not include identification information of a policy rule, and the network element of the core network determines that one or more policy rules are Policy rules used to establish this PDU session.
  • One or more of the above policy rules may default to the policy rules configured last time by the core network, or the policy rules configured by the core network at an agreed time/period, etc., which are not limited in this application.
  • the second sub-information may also include only the first indication information used to indicate identification (or use), or include the second indication information used to indicate unidentified (or unused), but not It includes the identification information of the PDU session, and does not include the identification information of the policy rule.
  • the network element of the core network determines, according to the first indication information or the second indication information, that one or more PDU sessions are established using or not using one or more policy rules.
  • One or more of the above PDU sessions can default to the last established PDU session, or a PDU session currently transmitting data streams, or a PDU session currently waiting to transmit data streams, or a PDU used by a certain agreed service or data stream For sessions, etc.
  • one or more of the above policy rules may default to the policy rules configured last time by the core network, or the policy rules configured by the core network at the agreed time/period, etc., which are not limited in this application.
  • the second sub-information is also used to indicate the mapping relationship between the PDU session and the policy rule used to establish the PDU session.
  • a PDU session may have a mapping relationship with one or more policy rules, and a policy rule may also have a mapping relationship with one or more PDU sessions.
  • the second sub-information may include a mapping relationship between identification information of a PDU session and identification information of a policy rule used to establish the PDU session.
  • policy rules used to establish the PDU session may include URSP, or may also include other policy rules, which is not limited in this application.
  • the third sub-information may include at least one set of mapping relationships between identification information of applications and identification information of policy rules, and each set of mapping relationships is used to indicate policy rules used for a certain application.
  • the third sub-information may include the identification information of at least one policy rule, but does not include the identification information of the application, and the network element of the core network determines that one or more applications use the identification information according to the identification information of the policy rule.
  • the policy rule corresponding to the information for example, it is determined that the data flow of one or more applications is transmitted using the PDU session established by the policy rule corresponding to the identification information.
  • One or more of the above-mentioned applications may default to an application that is currently transmitting data streams, or an application that is currently waiting to transmit data streams, or one or more agreed applications, etc., which is not limited in this application.
  • the third sub-information may include identification information of at least one application, but does not include identification information of a policy rule, and the network element of the core network determines that one or more policy rules are identified by the identification information according to the identification information of the application.
  • the application indicated by the information is used.
  • One or more of the above policy rules may default to the policy rules configured last time by the core network, or the policy rules configured by the core network at an agreed time/period, etc., which are not limited in this application.
  • the third sub-information may also only include the first indication information used to indicate identification (or use), or include the second indication information used to indicate unidentified (or unused), but not It includes the identification information of the application and does not include the identification information of the policy rule.
  • the network element of the core network determines that one or more applications use or do not use one or more policy rules according to the first indication information or the second indication information.
  • One or more of the above-mentioned applications can default to the application that is currently transmitting data streams, or the application that is currently waiting to transmit data streams, or one or more agreed applications, etc.
  • one or more of the above-mentioned policy rules can default to The policy rules configured last time by the core network, or the policy rules configured by the core network within the agreed time/period, etc., are not limited in this application.
  • the third sub-information is also used to indicate policy rules used by the application at different times or in different periods. For the same application, different policy rules may be used at different times or different periods, or the same policy rules may be used.
  • the third sub-information may include at least one set of mapping relationships between time/period and policy rules, and each set of mapping relationship is used to indicate the policy rule used by a certain application at a certain time/period.
  • the fourth sub-information may include at least one set of mapping relationships between the identification information of applications and the identification information of PDU sessions and/or network slices, each set of mapping relationships is used to indicate the PDU sessions and/or network slices.
  • the fourth sub-information may include identification information of at least one PDU session and/or network slice, but does not include identification information of an application
  • the network element of the core network may, according to the identification information of the PDU session and/or network slice, Determining that one or more applications use the PDU session and/or network slice corresponding to the identification information, for example, determining that the data flow of one or more applications is transmitted using the PDU session and/or network slice corresponding to the identification information.
  • One or more of the above-mentioned applications may default to an application that is currently transmitting data streams, or an application that is currently waiting to transmit data streams, or one or more agreed applications, etc., which is not limited in this application.
  • the fourth sub-information may include identification information of at least one application, but does not include identification information of PDU sessions and/or network slices, and the network element of the core network determines one or more The PDU session and/or network slice is used by the application indicated by the identification information.
  • One or more of the above PDU sessions and/or network slices can default to one or more agreed PDU sessions and/or network slices, such as the last established PDU session and/or network slice, or the currently transmitting data stream The PDU session and/or network slice, or the PDU session and/or network slice of the current data flow to be transmitted, etc., are not limited in this application.
  • the fourth sub-information may also only include the first indication information used to indicate recognition (or use), or include the second indication information used to indicate unidentified (or unused), but does not It includes identification information of applications, and does not include identification information of PDU sessions and/or network slices.
  • the network element of the core network determines that one or more applications use or do not use one or more PDU sessions and/or network slices according to the first indication information or the second indication information.
  • One or more of the above-mentioned applications can default to the application that is currently transmitting the data flow, or the application that is currently waiting to transmit the data flow, or one or more agreed applications, etc.; the above-mentioned one or more PDU sessions and/or A network slice can default to one or more agreed PDU sessions and/or network slices, such as the last established PDU session and/or network slice, or the PDU session and/or network slice currently transmitting data streams, or the current pending The PDU session and/or network slice of the transmission data flow, etc., are not limited in this application.
  • the fifth sub-information is used to indicate whether the terminal device has used the updated policy rule.
  • the fifth sub-information is used to indicate that the terminal device has used the updated policy rule, or the fifth sub-information is used to indicate that the terminal device has not used the updated policy rule.
  • the aforementioned updated policy rules may be updated by core network elements through downlink messages, such as UCU messages or other messages, which is not limited in this application.
  • the fifth sub-information may include indication information of one bit, which is used to indicate whether the terminal device has used the updated policy rule.
  • the fifth sub-information is used to indicate policy rules used by the terminal device. It should be noted that “used” here may mean “used” or “being used”. For example, the fifth sub-information is used to indicate the policy rule that the terminal device has used, or the fifth sub-information is used to indicate the policy rule that the terminal device is using. In some embodiments, the fifth sub-information may include identification information of the policy rule used by the terminal device, so as to indicate the policy rule used by the terminal device.
  • the fifth sub-information is used to indicate whether the terminal device has used the updated policy rule, and is used to indicate the policy rule used by the terminal device.
  • "use” here may mean “used” or “being used”. That is, in this example, the fifth sub-information has both the above two functions.
  • network slices may have different identifiers (such as S-NSSAI, NSI ID (Network Slice Instances ID, network slice instance identifier), etc.), taking S-NSSAI identifiers as an example, different network slices have different According to the S-NSSAI, terminal equipment and core network elements can distinguish different network slices according to the S-NSSAI.
  • the fourth sub-information is used to indicate the PDU session and/or network slice used for one or more applications, and there may be a mapping relationship between the PDU session and/or network slice and the policy rule, Then it is equivalent to indicating policy rules used for one or more applications.
  • the way of referring to the policy rule includes at least one of the following: using the Rule ID (rule identifier) of the policy rule to refer to; using one or more parameters of the policy rule to refer to. That is to say, the above-mentioned identification information of the policy rule can be represented by the Rule ID (or ID for short) of the policy rule, or can be represented by one or more parameters of the policy rule.
  • the Rule ID of a policy rule to refer to refers to using the Rule ID to uniquely refer to a policy rule.
  • the policy rule adopted by the terminal device is a URSP rule, and the URSP rule is referred to by URSPRule ID (URSP rule ID).
  • the RSD ID may be further used to refer to the RSD.
  • URSP Rule ID and RSD ID are used to refer to a URSP rule and the RSD under the URSP rule.
  • the policy rule adopted by the terminal device is a URSP rule
  • the Traffic descriptor (service descriptor) or Rule Precedence (rule priority) in the URSP rule is used to refer to the URSP rule.
  • Precedence (RSD priority) or Route selection components (routing selection components, that is, routing selection parameters) of RSD can also be used to refer to RSD.
  • the Traffic descriptor/Rule Precedence and the Precedence/Route selection components of the RSD in the URSP rule are used to refer to a URSP rule and the RSD under the URSP rule.
  • the policy rule indicated by the first information includes the URSP rule and/or at least one RSD under the URSP rule.
  • the terminal device sends the first information to the network element of the core network, and the first information includes information related to the use of the policy rules configured by the terminal device for the core network, so that the network element of the core network can know
  • the use of policy rules by terminal devices facilitates the configuration and update of subsequent policy rules and helps to improve communication reliability.
  • FIG. 10 shows a flowchart of a wireless communication method provided by another embodiment of the present application.
  • the method can be applied to the network architectures shown in FIG. 1 to FIG. 3 .
  • the method may include at least one of the following steps (1010-1020):
  • Step 1010 the network element of the core network sends a downlink message to the terminal device.
  • the downlink message includes policy rules configured by the core network for the terminal device.
  • the downlink message includes the URSP rule configured by the core network for the terminal device.
  • the URSP rule is used here as an example for illustration, and other rules and strategies introduced above may also be used, which is not limited in this application.
  • the policy rules refer to the content in other embodiments in the context, and this embodiment will not repeat them here.
  • the network element of the core network is a PCF. If the PCF wants to send a downlink message to the terminal device, it needs to send the downlink message to the AMF first, and the AMF forwards the downlink message to the terminal device. In some embodiments, the AMF does not perceive/modify the downlink message, and directly sends the downlink message sent by the PCF to the terminal device.
  • the downlink message is a UCU message.
  • the UCU message refers to a message sent by a core network element to a terminal device for instructing the terminal device to perform a configuration update.
  • the network element of the core network is a PCF, and the PCF puts the UCU message in the third container, sends the UCU message to the AMF through the third container, and sends the UCU message to the terminal device through the AMF.
  • the terminal device receives the downlink message sent by the network element of the core network.
  • Step 1020 the terminal device sends a response message corresponding to the downlink message to the network element of the core network, the reply message includes first information, and the first information includes information related to the use of policy rules configured by the terminal device for the core network.
  • the network element of the core network receives the reply message from the terminal device.
  • the terminal device after receiving the downlink message, evaluates the policy rules contained in the downlink message to determine the identified and/or unidentified policy rules; the terminal device evaluates the policy rules contained in the identified and/or unidentified policy rules; , generating the first message.
  • the downlink message includes a policy rule configured by the core network (such as PCF) for the terminal device, assuming it is policy rule 1, assuming that the terminal device evaluates the policy rule 1 and determines that it can identify (or agree with, or support, or use) ) of the policy rule 1, then the first information carried in the reply message sent by the terminal device to the network element of the core network may include the first indication information used to indicate identification (or approval, or support, or use).
  • the first information may further include identification information of the identified (or recognized, or supported, or used) policy rule 1.
  • the downlink message includes a policy rule configured by the core network (such as PCF) for the terminal device, assuming it is policy rule 1, assuming that the terminal device evaluates the policy rule 1 and determines that it is not recognized (or does not agree, or does not support, or not use) the policy rule 1, then the first information carried in the reply message sent by the terminal device to the core network element may include the 2. Instructions.
  • the first information may further include identification information of the unidentified (or not approved, or not supported, or not used) policy rule 1.
  • the downlink message includes multiple policy rules configured by the core network (such as PCF) for the terminal device, assuming that it includes policy rule 1 and policy rule 2, and assuming that the terminal device evaluates the policy rules 1 and 2 respectively, and determines that the identifiable ( or agree, or support, or use) the policy rule 1, but do not recognize (or do not agree with, or do not support, or not use) the policy rule 2, then the first A message that can be used to indicate that the terminal device can recognize (or agree with, or support, or use) the policy rule 1, and can also be used to indicate that the terminal device does not recognize (or do not agree with, or do not support, or do not use) the policy Rule 2 may also be used to indicate that the terminal device can recognize (or agree with, or support, or use) the policy rule 1 and not recognize (or not agree with, or not support, or not use) the policy rule 2.
  • the core network such as PCF
  • the reply message is contained in the first container.
  • the terminal device puts the reply message in the first container, and sends the reply message to the network element of the core network through the first container.
  • the network element of the core network is a PCF
  • the terminal device first sends the reply message to the AMF through the first container, and the AMF sends the reply message to the PCF without perception/modification.
  • the first information multiplexes existing fields in the reply message.
  • the existing fields in the reply message refer to the defined fields in the reply message. By reusing the existing fields to carry the first information, the format or fields of the reply message may not be modified.
  • the first information uses a newly added field in the reply message.
  • the new field in the reply message means that in order to carry the first information in the reply message, a new field is added in the reply message to carry the first information. In this way, only changes to the reply message are required and relatively small.
  • the first information is transmitted using a reply message in a newly defined format.
  • the above two methods use the original format of the reply message to carry the first information.
  • a new format is defined for the reply message, and the first information is transmitted through the newly defined format.
  • This design method is more flexible than the previous two, but needs to redefine the format of the reply message.
  • the downlink message is a UCU message and the terminal device transmits the first information in a reply message corresponding to the UCU message.
  • the terminal device adds first information to the reply message corresponding to the UCU message, where the first information is used to indicate the URSP rules that the terminal device can identify (or agree with, or support, or use).
  • a core network element (such as a PCF) sends a UCU message for UE policy configuration/update to the terminal device, and the UCU message includes the URSP rule configured by the core network element.
  • the terminal device evaluates the URSP rule contained in the UCU message to determine whether to support the parameters in the URSP rule. If one or more parameters in the URSP rule cannot be supported, then the terminal device determines that the URSP rule is not supported (or called unrecognized, or does not agree, or does not use).
  • the terminal device determines that it does not support (or is called unrecognized, or does not agree, or does not use) the RSD under the URSP rule, However, other RSDs under the URSP rule can still be supported (or all RSDs under the URSP rule can be considered not supported).
  • the terminal device may carry first information to indicate the URSP rule and/or RSD that the terminal device supports (and/or does not support).
  • the first information may also be called UE policy enforcement information, or URSP rule enforcement information, or other names, which are not limited in this application.
  • Policy Section Policy Section Code
  • the terminal device can reply based on which URSP rule in each policy segment and/or which RSD below it supports (or recognizes, or approves, or uses).
  • FIG. 11 to FIG. 15 exemplarily show the format of the reply message corresponding to the UCU message.
  • the message formats shown in Fig. 11 to Fig. 15 are nested layer by layer.
  • Figure 11 is a schematic diagram of the format of UE policy section management result information element (UE policy section management result information element). It can be seen from Figure 11 that the management result information element of each policy section includes UE policy section management result IEI (UE policy section management result information element identifier), Length of UE policy section management result contents (length of UE policy section management result content) and UE policy section management result contents (UE policy section management result content) .
  • UE policy section management result information element UE policy section management result information element identifier
  • Length of UE policy section management result contents length of UE policy section management result content
  • UE policy section management result contents UE policy section management result content
  • FIG 12 is a schematic diagram of the format of UE policy section management result contents (UE policy section management result content), as can be seen from Figure 12, UE policy section management result contents can include multiple UE policy section management subresult (UE policy section management subresult subresults), such as UE policy section management subresults corresponding to PLMN 1, PLMN 2, ..., PLMN N respectively.
  • UE policy section management subresult subres UE policy section management subresult subres
  • FIG 13 is a schematic diagram of the format of UE policy section management subresult (UE policy section management subresult), as can be seen from Figure 13, UE policy section management subresult can include Number of results (number of results), several MCC digit (country code code digits), several MNC digits (network operator code digits), and UE policy section management subresult contents (UE policy section management subresult contents).
  • Figure 14 is a schematic diagram of the format of UE policy section management subresult contents (UE policy section management subresult contents). 1), Result 2 (result 2), ..., Result N (result N), etc.
  • FIG. 15 is a schematic diagram of the format of Result (result).
  • Result can include UPSC (UPSC is used to indicate different parts of UE policy division under a PLMN), Failed instruction order (command failure command), Cause ( Reason value) and other fields.
  • UPSC UPSC is used to indicate different parts of UE policy division under a PLMN
  • Failed instruction order command failure command
  • Cause Reason value
  • the terminal device uses an existing field in a reply message corresponding to the UCU message to carry the foregoing first information.
  • the terminal device can reuse the Cause (cause value) field to carry the above-mentioned first information, indicating which URSP rule in a policy segment and/or which RSD below it supports (or identifies , or agree, or use).
  • the terminal device uses a newly added field in the reply message corresponding to the UCU message to carry the above-mentioned first information.
  • the terminal device adds a new field to carry the above-mentioned first information, indicating which URSP rule in a policy segment and/or which RSD below it supports (or identifies, or agrees, or use).
  • the terminal device transmits the first information using a reply message in a newly defined format.
  • the terminal device does not consider the issue of policy section in the reply message corresponding to the UCU message, and defines a new table (table) to indicate the URSP rules that the terminal device supports (or does not support). and/or its underlying RSD.
  • the table may include entries corresponding to a plurality of PLMNs, each entry is used to indicate a URSP rule supported (or not supported) by a PLMN and/or its underlying RSD.
  • the terminal device by carrying the first information used to indicate the use of the policy rules by the terminal device in the reply message corresponding to the downlink message (such as a UCU message), so that the network element of the core network can know that the terminal device uses the policy rules It facilitates the configuration and update of subsequent policy rules, and helps to improve communication reliability.
  • the downlink message such as a UCU message
  • FIG. 17 shows a flowchart of a wireless communication method provided by another embodiment of the present application.
  • the method can be applied to the network architectures shown in FIG. 1 to FIG. 3 .
  • the method may include the steps of:
  • Step 1710 the terminal device sends an uplink message to a network element of the core network, where the uplink message includes first information, and the first information includes information related to the use of policy rules configured by the terminal device for the core network.
  • the network element of the core network receives the uplink message from the terminal device.
  • the network element of the core network receives the uplink message from the terminal device.
  • the terminal device may actively send an uplink message to a network element of the core network, and report information related to the use of policy rules configured for the core network.
  • the uplink message is a UE state indication message, that is, a UE State Indication message (or called a UE STATE INDICATION message).
  • the terminal device sends a registration request message to a network element of the core network, and the registration request message includes a second container, and the second container includes an uplink message (such as a UE State Indication message).
  • the network element of the core network is a PCF
  • the terminal device sends a registration request message to the AMF
  • the registration request message contains the second container
  • the uplink message containing the first information is carried in the second container
  • the AMF receives the After the registration request message, the information in the second container is forwarded to the PCF.
  • the registration request message includes but not limited to at least one of the following: an initial registration request message, a periodic registration request message, and a location update registration request message.
  • the initial registration request message refers to the registration request message sent to the network element of the core network when the terminal device is initially turned on.
  • the periodic registration request message refers to the registration request message periodically sent by the terminal device to the network element of the core network.
  • the registration request message for location update refers to the registration request message sent to the network element of the core network when the location update of the terminal device occurs.
  • the terminal device when the first information changes, sends a registration request message including the changed first information to a network element of the core network. For example, when the first information changes, the terminal device actively sends a registration request message to the network element of the core network, and the registration request message contains the changed first information, so that the changed first information can be reported to the core network in a timely manner. network element.
  • the terminal device when the first information changes, the terminal device carries the changed first information in a registration request message sent to a network element of the core network triggered by other reasons.
  • other reasons include, but are not limited to, existing reasons for triggering registration request messages, such as registration request messages initiated under conditions such as initial power-on, expiration of a periodic timer, moving out of a registration area, and terminal capability update.
  • the terminal device uses a new field in the uplink message to carry the first information. For example, taking the uplink message as the UE state indication message as an example, a new field may be added in the UE state indication message to carry the first information.
  • the existing fields in the uplink message may also be reused to carry the first information, or the uplink message may also be other uplink messages except the UE status indication message, which is not limited in this application.
  • the following table 3 exemplarily shows a schematic diagram of message content of a UE state indication message (UE STATE INDICATION message).
  • FIG. 18 it exemplarily shows a flowchart of a terminal device (shown as UE in the figure) sending a registration request message to a core network element (shown as PCF in the figure).
  • the registration request message the first information introduced above may be carried.
  • the process may include the following steps:
  • Step 1810 the UE sends a Registration Request (registration request) message to the (R)AN;
  • Step 1820 (R) AN sends a Registration Request message to AMF;
  • Step 1830 AM Policy Association Establishment/Modification (AM Policy Association Establishment/Modification) process is performed between AMF and PCF;
  • step 1840 the AMF sends a Registration Accept message to the UE.
  • the Registration Request message contains a container (that is, the "second container” introduced in the above embodiment), the UE State Indication message containing the first information is carried in the container, and the AMF receives the Registration Request message Afterwards, in the process of establishing/modifying the AM policy association between the AMF and the PCF, the AMF forwards the information in the container to the PCF, so that the first information is reported to the network side during the terminal registration request process.
  • the Registration Request message may be an initial Registration Request message, a periodic Registration Request message, a Registration Request message for location update, etc., which is not limited in this application.
  • the AMF calls the Npcf_UEPolicyControl Service service, and forwards the information in the container to the PCF through the Npcf_UEPolicyControl Service service.
  • the reply message corresponding to the registration request sent by the AMF to the UE may indicate that the registration is completed (such as a Registration Accept message), or may indicate that the registration is rejected, which is not limited in this application.
  • the terminal device by carrying the first information used to indicate the use of policy rules by the terminal device in the uplink message (such as UE status indication message), the active reporting of the use of policy rules is realized, so that the core network
  • the unit can know the use of policy rules by terminal devices, which facilitates the configuration and update of subsequent policy rules, and helps to improve communication reliability.
  • FIG. 19 shows a flowchart of a wireless communication method provided by another embodiment of the present application.
  • the method can be applied to the network architectures shown in FIG. 1 to FIG. 3 .
  • the method may include the steps of:
  • Step 1910 the terminal device sends a PDU session establishment/modification request to the network element of the core network, the PDU session establishment/modification request includes first information, and the first information includes information related to the use of policy rules configured by the terminal device for the core network information.
  • the network element of the core network receives the PDU session establishment/modification request from the terminal device.
  • the network element of the core network receives the PDU session establishment/modification request from the terminal device.
  • the terminal device may carry the first information that needs to be reported to the core network in the PDU session establishment request and/or the PDU session establishment request.
  • the terminal device may carry the first information that needs to be reported to the core network in the PDU session establishment request and/or the PDU session establishment request.
  • the terminal device sends a PDU session establishment/modification request to a network element of the core network, and the PDU session establishment/modification request includes first information in addition to the PDU session parameters.
  • the terminal device sends a PDU session establishment/modification request to the SMF, and after the SMF receives the PDU session establishment/modification request, the SMF sends a reply message corresponding to the PDU session establishment/modification request to the terminal device. If the SMF rejects the PDU session establishment/modification request, the reply message corresponding to the PDU session establishment/modification request includes the rejection reason value.
  • the terminal device can re-initiate the PDU session modification request according to the RSD parameter adjustment parameter combination of the URSP rule, and the SMF makes a corresponding reply after receiving the PDU session modification request.
  • the SMF may obtain the first information from it, and send the first information to the PCF.
  • the terminal device when the first information changes, sends a PDU session establishment/modification request including the changed first information to a network element of the core network. For example, when the first information changes, the terminal device actively sends a PDU session establishment/modification request to the network element of the core network, and the PDU session establishment/modification request contains the changed first information, so that the changed first The information is reported to the core network elements in a timely manner.
  • the terminal device when the first information changes, the terminal device carries the changed first information in the PDU session establishment/modification request sent to the network element of the core network triggered by other reasons.
  • other reasons include but are not limited to existing reasons for triggering the PDU session establishment/modification request, such as when the establishment condition of the PDU session is satisfied, the modification condition of the PDU session is satisfied, etc., which are not limited in this application.
  • the terminal device uses a newly added field in the PDU session establishment/modification request to carry the first information.
  • a new field may be added in the PDU session establishment/modification request to carry the first information.
  • the existing fields in the PDU session establishment/modification request may also be reused to carry the first information, which is not limited in this application.
  • the report of the use of policy rules is realized, so that the network elements of the core network can know the terminal.
  • the device's use of policy rules facilitates the configuration and update of subsequent policy rules and helps improve communication reliability.
  • reporting the first information includes reporting the first information based on the UCU process and reporting the first information based on the terminal registration process . Reporting the first information and the like based on the PDU session establishment/modification process. It can be understood that the terminal device may also carry the first information in other uplink messages or reply messages corresponding to the downlink messages, so as to report the first information to the core network. All these should be within the protection scope of the present application, and the embodiments of the present application will not give examples one by one.
  • the terminal device before the terminal device sends the first information to the network element of the core network, there may also be a process described in the following exemplary embodiments.
  • the terminal device sends the first indication to the network element of the core network, and correspondingly, the network element of the core network receives the first indication sent by the terminal device, where the first indication is used to indicate that the terminal device supports reporting of the first information and/or or at least one sub-information in the first information.
  • the core network element may be a PCF.
  • the above-mentioned first indication can also be regarded as a capability indication of the terminal device, which is used to inform the core network whether the terminal device supports (or requests, or allows, or requires, that is, this parameter can let the network side know that the terminal device can report the first Information) to report the first information, and/or, used to inform the core network that the terminal device supports (or requests, or allows, or requires, that is, this parameter can make the terminal device know that it needs to report the first information) to report the first information Which or which sub-information of .
  • the first indication is used to indicate that the terminal device supports reporting of the first information, and supports reporting of the first sub-information and the second sub-information in the first information.
  • the network element of the core network may decide whether to allow the terminal device to report the first information, and/or allow or not allow the terminal device to report which or which sub-information in the first information, and then apply the above decision The result is sent to the terminal device, so that the terminal device can report the first information according to the requirement of the network side.
  • the core network element sends the second indication to the terminal device, and the terminal device receives the second indication from the core network element, and the second indication is used to instruct the core network element to support the terminal device to report the first information and /or at least one sub-information in the first information.
  • the core network element may be a PCF.
  • the above-mentioned second indication can also be regarded as a demand indication on the network side, which is used to inform the terminal device whether the core network supports (or allows, or requests) to report the first information, and/or is used to inform the terminal device that the core network
  • the network supports (or allows, or requests) which sub-information in the first information to report is used to indicate that the core network supports reporting of the first information, and supports reporting of the first sub-information and the third sub-information in the first information.
  • the terminal device may decide whether to report the first information to the core network, and/or which or which sub-information in the first information to report, so that the terminal device can perform the first information according to the requirements of the network side. Reporting of information.
  • the terminal device sends the first indication to the network element of the core network, and the subsequent terminal device may report the first information to the network element of the core network according to the first indication.
  • the first indication is used to indicate that the terminal device supports reporting of the first information and supports reporting of the first sub-information and the second sub-information in the first information, then the first information reported by the terminal device to the network element of the core network includes the first sub-information and second sub-information.
  • the network element of the core network receives the first indication, it can determine according to the first indication whether the terminal device will report the first information, and in the case of reporting the first information, it will report the Which or which sub-information, so as to accurately receive the first information.
  • the terminal device sends the first indication to the network element of the core network, but the network element of the core network does not need to send the second indication to the terminal device.
  • the core network element sends the second indication to the terminal device, and the subsequent terminal device may report the first information to the core network element according to the second indication. For example, if the second indication is used to indicate that the core network element supports the terminal device to report the first information, then the terminal device reports the first information to the core network element; if the second indication is used to indicate that the core network element does not support the terminal device to report first information, then the terminal device does not report the first information to the network element of the core network.
  • the second indication is used to instruct the core network element to support the terminal device to report one or several sub-information in the first information
  • the first information reported by the terminal device to the core network element carries the above core
  • the sub-information supported by the network element, and the sub-information that the core network element does not support reporting may not be reported by the terminal equipment, thereby avoiding unnecessary information transmission.
  • the core network element sends the second indication to the terminal device, but the terminal device does not need to send the first indication to the core network element.
  • one of these two processes may be executed, or both may be executed. In the case of performing both, it can be implemented as a negotiation process between the terminal equipment and the core network.
  • the terminal device sends a first indication to a network element of the core network, where the first indication is used to indicate that the terminal device supports reporting of the first information and/or at least one sub-information in the first information; and, the core network The element sends a second indication to the terminal device, where the second indication is used to instruct the network element of the core network to support the terminal device to report the first information and/or at least one sub-information in the first information. That is, during the negotiation process, the terminal device sends the first indication to the network element of the core network, and the network element of the core network sends the second indication to the terminal device.
  • the terminal device may first send the first indication to the network element of the core network, and then the network element of the core network sends the second indication to the terminal device; or, It is also possible that the core network element sends the second instruction to the terminal device first, and then the terminal device sends the first instruction to the core network element; or, the sending process of the first instruction and the second instruction is executed simultaneously, which is not limited in this application .
  • the first indication is used to indicate that the terminal device supports reporting of the first information, and supports reporting of the first sub-information and the second sub-information in the first information
  • the second indication is used to indicate that the core network supports reporting of the first information, and supports Report the first sub-information and the third sub-information in the first information.
  • the above-mentioned sending of the first indication and the second indication may occur during the UCU process, and may also occur during the terminal registration process.
  • the above-mentioned first indication and second indication may also be sent using a dedicated message, or carried in other existing messages, which is not limited in this application.
  • the UCU message sent by the network element of the core network to the terminal device includes the second indication, and/or, the reply message corresponding to the UCU message includes the first indication .
  • the terminal device sends the first indication in the reply message corresponding to the UCU message, then if it is determined to report the first information, the first information may be carried in the reply message corresponding to the UCU message, or may be sent when the UCU message is sent. The first message is sent after the reply message corresponding to the message, which is not limited in this application.
  • the registration request message sent by the terminal device to the network element of the core network includes the first indication, and/or, the reply message corresponding to the registration request message includes Second instruction.
  • the terminal device sends the first indication in the registration request message, then if it is determined to report the first information, the first information may be carried in the registration request message, or may be received after receiving a reply corresponding to the registration request message The first information is sent after the message, which is not limited in this application.
  • the PDU session establishment/modification request sent by the terminal device to the network element of the core network includes the first indication, and/or, the PDU session establishment The reply message corresponding to the /modification request includes the second indication.
  • the terminal device sends the first indication in the PDU session establishment/modification request, then if it is determined to report the first information, the first information may be carried in the PDU session establishment/modification request, or may be received The first information is sent after the reply message corresponding to the PDU session establishment/modification request, which is not limited in this application.
  • the control of the information reported by the terminal on the network side is realized, unnecessary information transmission is avoided, and transmission resources are saved.
  • FIG. 20 shows a block diagram of a wireless communication device provided by an embodiment of the present application.
  • the apparatus may be realized as a terminal device, or may be realized as a part of the terminal device.
  • the apparatus 2000 may include: a sending module 2010 .
  • the sending module 2010 is configured to send first information to a network element of the core network, where the first information includes information related to usage of policy rules configured by the terminal device for the core network.
  • the first information includes at least one of the following:
  • the first sub-information is used to indicate identified and/or unidentified policy rules
  • the second sub-information is used to indicate the policy rule used to establish the PDU session
  • the third sub-information is used to indicate policy rules used for one or more applications.
  • the fourth sub-information is used to indicate the PDU session and/or network slice used for one or more applications
  • the fifth sub-information is used to indicate whether the terminal device has used the updated policy rule and/or the policy rule used by the terminal device.
  • the second sub-information is also used to indicate a mapping relationship between the PDU session and the policy rule used to establish the PDU session.
  • the third sub-information is also used to indicate policy rules used for the application at different times or in different periods.
  • the network slice is identified by S-NSSAI.
  • the sending module 2010 is configured to, after receiving the downlink message sent by the network element of the core network, send a reply message corresponding to the downlink message to the network element of the core network, the reply message includes the first information.
  • the apparatus 2000 further includes a processing module 2020, configured to, after receiving the downlink message, evaluate the policy rule contained in the downlink message, determine the identification and/or or an unidentified policy rule; generating the first information according to the identified and/or unidentified policy rule.
  • a processing module 2020 configured to, after receiving the downlink message, evaluate the policy rule contained in the downlink message, determine the identification and/or or an unidentified policy rule; generating the first information according to the identified and/or unidentified policy rule.
  • the reply message is contained in a first container.
  • the downlink message is a UCU message.
  • the first information reuses existing fields in the reply message, or the first information uses newly added fields in the reply message.
  • the first information is transmitted using the reply message in a newly defined format.
  • the sending module 2010 is configured to send an uplink message to the core network element, where the uplink message includes the first information.
  • the sending module 2010 is configured to send a registration request message to the network element of the core network, where the registration request message includes a second container, and the second container includes the uplink message.
  • the registration request message includes at least one of the following: an initial registration request message, a periodic registration request message, and a location update registration request message.
  • the sending module 2010 is further configured to, when the first information changes, send a registration request message containing the changed first information to the network element of the core network, or trigger the registration due to other reasons.
  • the registration request message sent to the network element of the core network carries the changed first information.
  • the uplink message is a UE status indication message.
  • a new field in the uplink message is used to carry the first information.
  • the sending module 2010 is configured to send a PDU session establishment/modification request to the core network element, where the PDU session establishment/modification request includes the first information.
  • the sending module 2010 is configured to send a first indication to the network element of the core network, where the first indication is used to indicate that the terminal device supports reporting of the first information and/or the at least one sub-information in the first information;
  • the apparatus 2000 further includes a receiving module (not shown in FIG. 20 ), configured to receive a second indication from the network element of the core network, where the second indication is used to indicate that the network element of the core network Supporting the terminal device to report the first information and/or at least one sub-information in the first information.
  • a receiving module (not shown in FIG. 20 ), configured to receive a second indication from the network element of the core network, where the second indication is used to indicate that the network element of the core network Supporting the terminal device to report the first information and/or at least one sub-information in the first information.
  • the UCU message sent by the core network element to the terminal device includes the second indication, and/or, the UCU The reply message corresponding to the message includes the first indication.
  • the registration request message sent by the terminal device to the network element of the core network includes the first indication, and/or, the The reply message corresponding to the registration request message includes the second indication.
  • the PDU session establishment/modification request sent by the terminal device to the core network element includes the first indication
  • the reply message corresponding to the PDU session establishment/modification request includes the second indication
  • the referring manner of the policy rule includes at least one of the following:
  • One or more parameters of the policy rule are used for referral.
  • one or more parameters of the policy rule are used for referencing, including: using the Traffic descriptor and/or Rule Precedence of the URSP rule, referring to Substitute the URSP rule; and/or, use the Precedence and/or Route selection components of the RSD under the URSP rule to refer to the RSD under the URSP rule.
  • the policy rules include at least one of the following: URSP, V2XP, ProSeP, and ANDSP.
  • the policy rule indicated by the first information includes a URSP rule and/or at least one RSD under the URSP rule.
  • FIG. 21 shows a block diagram of a wireless communication device provided by another embodiment of the present application.
  • the device can be realized as a network element of the core network, or can be realized as a part of the network element of the core network.
  • the apparatus 2100 may include: a receiving module 2110 .
  • the receiving module 2110 is configured to receive first information from the terminal device, where the first information includes information related to the use of policy rules configured by the terminal device for the core network.
  • the first information includes at least one of the following:
  • the first sub-information is used to indicate identified and/or unidentified policy rules
  • the second sub-information is used to indicate the policy rule used to establish the PDU session
  • the third sub-information is used to indicate policy rules used for one or more applications.
  • the fourth sub-information is used to indicate the PDU session and/or network slice used for one or more applications
  • the fifth sub-information is used to indicate whether the terminal device has used the updated policy rule and/or the policy rule used by the terminal device.
  • the second sub-information is further used to indicate a mapping relationship between the PDU session and the policy rule used to establish the PDU session.
  • the third sub-information is also used to indicate policy rules used for the application at different times or in different periods.
  • the network slice is identified by S-NSSAI.
  • the receiving module 2110 is configured to receive a reply message corresponding to the downlink message from the terminal device after the core network element sends the downlink message to the terminal device, wherein the reply message including the first information.
  • the policy rules included in the downlink message are used to be evaluated by the terminal device, and the first information is generated after identifying and/or unidentified policy rules are determined.
  • the reply message is contained in a first container.
  • the downlink message is a UCU message.
  • the first information reuses existing fields in the reply message, or the first information uses newly added fields in the reply message.
  • the first information is transmitted using the reply message in a newly defined format.
  • the receiving module 2110 is configured to receive an uplink message from the terminal device, where the uplink message includes the first information.
  • the receiving module 2110 is configured to receive a registration request message from the terminal device, the registration request message includes a second container, and the second container includes the uplink message.
  • the registration request message includes at least one of the following: an initial registration request message, a periodic registration request message, and a location update registration request message.
  • the receiving module 2110 is further configured to receive a registration request message containing the changed first information sent by the terminal device when the first information changes, or trigger the registration request message for other reasons.
  • the registration request message sent by the terminal device carries the changed first information.
  • the uplink message is a UE status indication message.
  • a new field in the uplink message is used to carry the first information.
  • the receiving module 2110 is configured to receive a PDU session establishment/modification request sent by the terminal device, where the PDU session establishment/modification request includes the first information.
  • the receiving module 2110 is configured to receive a first indication sent by the terminal device, where the first indication is used to indicate that the terminal device supports reporting of the first information and/or the first at least one sub-information in the message;
  • the apparatus 2100 further includes a sending module (not shown in FIG. 21 ), configured to send a second indication to the terminal device, where the second indication is used to indicate that the core network element supports the The terminal device reports the first information and/or at least one sub-information in the first information.
  • a sending module (not shown in FIG. 21 ), configured to send a second indication to the terminal device, where the second indication is used to indicate that the core network element supports the The terminal device reports the first information and/or at least one sub-information in the first information.
  • the UCU message sent by the core network element to the terminal device includes the second indication, and/or, the UCU The reply message corresponding to the message includes the first indication.
  • the registration request message sent by the terminal device to the network element of the core network includes the first indication, and/or, the The reply message corresponding to the registration request message includes the second indication.
  • the PDU session establishment/modification request sent by the terminal device to the core network element includes the first indication
  • the reply message corresponding to the PDU session establishment/modification request includes the second indication
  • the referring manner of the policy rule includes at least one of the following:
  • One or more parameters of the policy rule are used for referral.
  • one or more parameters of the policy rule are used for referencing, including: using the Traffic descriptor and/or Rule Precedence of the URSP rule, referring to Substitute the URSP rule; and/or, use the Precedence and/or Route selection components of the RSD under the URSP rule to refer to the RSD under the URSP rule.
  • the policy rules include at least one of the following: URSP, V2XP, ProSeP, and ANDSP.
  • the policy rule indicated by the first information includes a URSP rule and/or at least one RSD under the URSP rule.
  • the terminal device 2200 may include: a processor 2201 , a transceiver 2202 and a memory 2203 .
  • the processor 2201 includes one or more processing cores, and the processor 2201 executes various functional applications and information processing by running software programs and modules.
  • the transceiver 2202 may include a receiver and a transmitter.
  • the receiver and the transmitter may be implemented as the same wireless communication component, and the wireless communication component may include a wireless communication chip and a radio frequency antenna.
  • the memory 2203 may be connected to the processor 2201 and the transceiver 2202 .
  • the memory 2203 may be used to store a computer program executed by the processor, and the processor 2201 is used to execute the computer program, so as to implement various steps performed by the terminal device in the foregoing method embodiments.
  • volatile or non-volatile storage device includes but not limited to: magnetic disk or optical disk, electrically erasable and programmable Read Only Memory, Erasable Programmable Read Only Memory, Static Anytime Access Memory, Read Only Memory, Magnetic Memory, Flash Memory, Programmable Read Only Memory.
  • the transceiver 2202 is configured to send first information to a network element of the core network, where the first information includes information related to usage of policy rules configured by the terminal device for the core network.
  • the network device 2300 may include: a processor 2301 , a transceiver 2302 and a memory 2303 .
  • the processor 2301 includes one or more processing cores, and the processor 2301 executes various functional applications and information processing by running software programs and modules.
  • Transceiver 2302 may include a receiver and a transmitter.
  • the transceiver 2302 may include a wired communication component, and the wired communication component may include a wired communication chip and a wired interface (such as an optical fiber interface).
  • the transceiver 2302 may also include a wireless communication component, and the wireless communication component may include a wireless communication chip and a radio frequency antenna.
  • the memory 2303 may be connected to the processor 2301 and the transceiver 2302 .
  • the memory 2303 may be used to store a computer program executed by the processor, and the processor 2301 is used to execute the computer program, so as to implement various steps performed by the network elements of the core network in the foregoing method embodiments.
  • the memory 2303 can be implemented by any type of volatile or non-volatile storage device or their combination.
  • the volatile or non-volatile storage device includes but not limited to: magnetic disk or optical disk, electrically erasable and programmable Read Only Memory, Erasable Programmable Read Only Memory, Static Anytime Access Memory, Read Only Memory, Magnetic Memory, Flash Memory, Programmable Read Only Memory.
  • the transceiver 2302 when the network device is a network element of the core network, the transceiver 2302 is configured to receive first information sent by the terminal device, where the first information includes policy rules configured by the terminal device for the core network information about the usage of .
  • An embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a terminal device, so as to implement the above wireless communication method on the terminal device side.
  • the embodiment of the present application also provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used to be executed by a processor of a network device (such as a core network element) to implement the above-mentioned network A wireless communication method on the side of a device (such as a network element of a core network).
  • a network device such as a core network element
  • the computer-readable storage medium may include: ROM (Read-Only Memory, read-only memory), RAM (Random-Access Memory, random access memory), SSD (Solid State Drives, solid state drive) or an optical disc, etc.
  • the random access memory may include ReRAM (Resistance Random Access Memory, resistive random access memory) and DRAM (Dynamic Random Access Memory, dynamic random access memory).
  • the embodiment of the present application also provides a chip, the chip includes a programmable logic circuit and/or program instructions, and when the chip runs on the terminal device, it is used to implement the above wireless communication method on the terminal device side.
  • the embodiment of the present application also provides a chip, the chip includes a programmable logic circuit and/or program instructions, and when the chip runs on a network device (such as a core network element), it is used to realize the above-mentioned network device (such as the wireless communication method on the side of the network element of the core network.
  • a network device such as a core network element
  • the embodiment of the present application also provides a computer program product or computer program, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and the processor of the terminal device reads from the computer The readable storage medium reads and executes the computer instructions, so as to implement the above wireless communication method on the terminal device side.
  • the embodiment of the present application also provides a computer program product or computer program, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and network devices (such as core network elements)
  • the processor reads and executes the computer instructions from the computer-readable storage medium, so as to implement the above wireless communication method on the side of the network device (such as a network element of the core network).
  • the "indication" mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship.
  • a indicates B which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and is configuration etc.
  • predefined can be realized by pre-saving corresponding codes, tables, or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). Its specific implementation manner is not limited. For example, the predefined ones may refer to those defined in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, for example, may include LTE protocol, NR protocol and related protocols applied in future communication systems, which is not limited in the present application.
  • the "plurality” mentioned herein means two or more.
  • “And/or” describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently.
  • the character “/” generally indicates that the contextual objects are an "or” relationship.
  • the numbering of the steps described herein only exemplarily shows a possible sequence of execution among the steps.
  • the above-mentioned steps may not be executed according to the order of the numbers, such as two different numbers
  • the steps are executed at the same time, or two steps with different numbers are executed in the reverse order as shown in the illustration, which is not limited in this embodiment of the present application.
  • the functions described in the embodiments of the present application may be implemented by hardware, software, firmware or any combination thereof.
  • the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a storage media may be any available media that can be accessed by a general purpose or special purpose computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种无线通信方法、装置、设备、存储介质及程序产品，涉及通信技术领域，所述方法包括，终端设备向核心网网元发送第一信息，第一信息包括终端设备针对策略规则的使用情况相关的信息(910)。本申请通过终端设备向核心网网元发送第一信息，该第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息，使得核心网网元可以知晓终端设备对于策略规则的使用情况，便于后续策略规则的配置及更新，有助于提升通信可靠性。

Description

无线通信方法、装置、设备、存储介质及程序产品 技术领域
本申请实施例涉及通信技术领域，特别涉及一种无线通信方法、装置、设备、存储介质及程序产品。
背景技术
核心网可以向终端设备提供一些策略规则(如URSP(UE Route Selection Policy，UE路由选择策略)、ANDSP(Access Network Discovery&Selection Policy，接入网发现和选择策略)等)，以供终端设备和网络侧能够进行通信。
对于终端设备针对核心网配置的策略规则的使用，目前还需进一步研究。
发明内容
本申请实施例提供了一种无线通信方法、装置、设备、存储介质及程序产品。所述技术方案如下：
根据本申请实施例的一个方面，提供了一种无线通信方法，所述方法包括：
终端设备向核心网网元发送第一信息，所述第一信息包括所述终端设备针对核心网配置的策略规则的使用情况相关的信息。
根据本申请实施例的一个方面，提供了一种无线通信方法，所述方法包括：
核心网网元接收来自终端设备的第一信息，所述第一信息包括所述终端设备针对核心网配置的策略规则的使用情况相关的信息。
根据本申请实施例的一个方面，提供了一种无线通信装置，所述装置包括：
发送模块，用于向核心网网元发送第一信息，所述第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息。
根据本申请实施例的一个方面，提供了一种无线通信装置，所述装置包括：
接收模块，用于接收来自终端设备的第一信息，所述第一信息包括所述终端设备针对核心网配置的策略规则的使用情况相关的信息。
根据本申请实施例的一个方面，提供了一种通信设备，所述通信设备包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述计算机程序以实现上述终端设备侧的无线通信方法，或者上述核心网网元侧的无线通信方法。
根据本申请实施例的一个方面，提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，所述计算机程序由处理器加载并执行以实现上述终端设备侧的无线通信方法，或者上述核心网网元侧的无线通信方法。
根据本申请实施例的一个方面，提供了一种芯片，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片运行时，用于实现上述终端设备侧的无线通信方法，或者上述核心网网元侧的无线通信方法。
根据本申请实施例的一个方面，提供了一种计算机程序产品或计算机程序，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，处理器从所述计算机可读存储介质读取并执行所述计算机指令，以实现上述终端设备侧的无线通信方法，或者上述核心网网元侧的无线通信方法。
本申请实施例提供的技术方案可以包括如下有益效果：
通过终端设备向核心网网元发送第一信息，该第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息，使得核心网网元可以知晓终端设备对于策略规则的使用情况，便于后续策略规则的配置及更新，有助于提升通信可靠性。
附图说明
图1是本申请一个实施例提供的网络架构的示意图；
图2是本申请一个实施例提供的5G系统的架构图；
图3是本申请另一个实施例提供的5G系统的架构图；
图4是本申请一个实施例提供的UE(User Equipment，用户设备)策略配置的流程图；
图5是本申请一个实施例提供的PCF(Policy Control Function，策略控制功能)和UE之间消息交互 的流程图；
图6是本申请另一个实施例提供的PCF和UE之间消息交互的流程图；
图7是本申请一个实施例提供的应用数据流根据URSP绑定到PDU(Packet Data Unit，分组数据单元)会话的示意图；
图8是本申请一个实施例提供的PDU会话建立拒绝和再次尝试的流程图；
图9是本申请一个实施例提供的无线通信方法的流程图；
图10是本申请另一个实施例提供的无线通信方法的流程图；
图11至图15是本申请一个实施例提供的UCU消息对应的回复消息的格式示意图；
图16是本申请另一个实施例提供的UCU消息对应的回复消息的格式示意图；
图17是本申请另一个实施例提供的无线通信方法的流程图；
图18是本申请一个实施例提供的UE向核心网网元发送注册请求消息的流程图；
图19是本申请另一个实施例提供的无线通信方法的流程图；
图20是本申请另一个实施例提供的无线通信装置的框图；
图21是本申请另一个实施例提供的无线通信装置的框图；
图22是本申请一个实施例提供的终端设备的结构示意图；
图23是本申请一个实施例提供的网络设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
本申请实施例描述的网络架构以及业务场景是为了更加清楚地说明本申请实施例的技术方案，并不构成对本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、非授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、非授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、非地面通信网络(Non-Terrestrial Networks，NTN)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、第五代通信(5th-Generation，5G)系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，车辆间(Vehicle to Vehicle，V2V)通信，或车联网(Vehicle to everything，V2X)通信等，本申请实施例也可以应用于这些通信系统。
本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
本申请实施例中的通信系统可以应用于非授权频谱，其中，非授权频谱也可以认为是共享频谱；或者，本申请实施例中的通信系统也可以应用于授权频谱，其中，授权频谱也可以认为是非共享频谱。
本申请实施例可应用于非地面通信网络(Non-Terrestrial Networks，NTN)系统，也可应用于地面通信网络(Terrestrial Networks，TN)系统。
请参考图1，其示出了本申请一个实施例提供的网络架构的示意图。该网络架构可以包括：终端设备10、接入网设备20和核心网网元30。
终端设备10可以指UE、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、无线通信设备、用户代理或用户装置。在一些实施例中，终端设备10还可以是蜂窝电话、无绳电话、SIP(Session Initiation Protocol，会话启动协议)电话、WLL(Wireless Local Loop，无线本地环路)站、PDA(Personal Digita1Assistant，个人数字处理)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，5GS(5th Generation System，第五代移动通信系统)中的终端设备或者未来演进的PLMN(Pub1ic Land Mobi1e Network，公用陆地移动通信网络)中的终端设备等，本申请实施例对此并不限定。为方便描述，上面提到的设备统称为终端设备。终端设备10的数量通常为多个，每一个接入网设备20所管理的小区内可以分布一个或多个终端设备10。在本申请实 施例中，“终端设备”和“UE”通常混用，但本领域技术人员可以理解其含义。
接入网设备20是一种部署在接入网中用以为终端设备10提供无线通信功能的设备。接入网设备20可以包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，具备接入网设备功能的设备的名称可能会有所不同，例如在5G NR系统中，称为gNodeB或者gNB。随着通信技术的演进，“接入网设备”这一名称可能会变化。为方便描述，本申请实施例中，上述为终端设备10提供无线通信功能的装置统称为接入网设备。在一些实施例中，通过接入网设备20，终端设备10和核心网网元30之间可以建立通信关系。示例性地，在LTE(Long Term Evolution，长期演进)系统中，接入网设备20可以是EUTRAN(Evolved Universal Terrestrial Radio Access Network，演进的通用陆地无线网)或者EUTRAN中的一个或者多个eNodeB；在5G NR系统中，接入网设备20可以是RAN(Radio Access Network，无线接入网)或者RAN中的一个或者多个gNB。
核心网网元30是部署在核心网中的网元，核心网网元30的功能主要是提供用户连接、对用户的管理以及对业务完成承载，作为承载网络提供到外部网络的接口。例如，5G NR系统中的核心网网元可以包括AMF(Access and Mobility Management Function，接入和移动性管理功能)、UPF(User Plane Function，用户平面功能)和SMF(Session Management Function，会话管理功能)等网元。另外，核心网网元可以看作是功能实体，一台物理设备上可以部署一个或者多个核心网网元。
在一些实施例中，接入网设备20与核心网网元30之间通过某种空口技术互相通信，例如5G NR系统中的NG接口。接入网设备20与终端设备10之间通过某种空口技术互相通信，例如Uu接口。
本申请实施例中的“5G NR系统”也可称为5G系统或者NR系统，但本领域技术人员可以理解其含义。本申请实施例描述的技术方案可以适用于LTE系统，也可以适用于5G NR系统，也可以适用于5G NR系统后续的演进系统，还可以适用于诸如NB-IoT(Narrow Band Internet of Things，窄带物联网)系统等其他通信系统，本申请对此不作限定。
在本申请实施例中，接入网设备可以为小区提供服务，终端设备通过该小区使用的载波上的传输资源(例如，频域资源，或者说，频谱资源)与接入网设备进行通信，该小区可以是接入网设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
请参考图2，其示出了本申请实施例提供的5GS(5th Generation System，第五代移动通信系统)的系统架构的示意图。如图2所示，该系统架构200可以包括：UE(也即上文介绍的“终端设备”)、(R)AN((Radio)Access Network，(无线)接入网)、Core(核心网)和DN(Data Network，数据网络)。其中，UE、(R)AN、Core是构成架构的主要成分，逻辑上它们可以分为用户面和控制面两部分，控制面负责移动网络的管理，用户面负责业务数据的传输。图中，NG2参考点位于(R)AN控制面和Core控制面之间，NG3参考点位于(R)AN用户面和Core用户面之间，NG6参考点位于Core用户面和数据网络之间。
UE：是移动用户与网络交互的入口，能够提供基本的计算能力、存储能力，向用户显示业务窗口，接收用户操作输入。UE会采用下一代空口技术，与(R)AN建立信号连接、数据连接，从而传输控制信号和业务数据到移动网络。
(R)AN：类似于传统网络里面的基站，部署在靠近UE的位置，为特定区域的授权用户提供入网功能，并能够根据用户的级别，业务的需求等使用不同质量的传输隧道传输用户数据。(R)AN能够管理自身的资源，合理利用，按需为UE提供接入服务，把控制信号和用户数据在UE和核心网之间转发。
Core：负责维护移动网络的签约数据，管理移动网络的网元，为UE提供会话管理、移动性管理、策略管理、安全认证等功能。在UE附着的时候，为UE提供入网认证；在UE有业务请求时，为UE分配网络资源；在UE移动的时候，为UE更新网络资源；在UE空闲的时候，为UE提供快恢复机制：在UE去附着的时候，为UE释放网络资源；在UE有业务数据时，为UE提供数据路由功能，如转发上行数据到DN：或者从DN接收UE下行数据，转发到(R)AN，从而发送给UE。
DN：是为用户提供业务服务的数据网络，一般客户端位于UE，服务端位于数据网络。数据网络可以是私有网络，如局域网，也可以是不受运营商管控的外部网络，如Internet，还可以是运营商共同部署的专有网络，如为了配置IMS(IP Multimedia Core Network Subsystem，IP多媒体网络子系统)服务。
图3是在图2的基础上确定的详细架构，其中核心网用户面包括UPF(User Plane Function，用户面功能)；核心网控制面包括AUSF(Authentication Server Function，认证服务器功能)、AMF、SMF、NSSF(Network Slice Selection Function，网络切片选择功能)、NEF(Network Exposure Function，网络开放功能)、NRF(Network Repository Function，网络存储功能)、UDM(Unified Data Management，统一数据管理)、PCF、AF(Application Function，应用功能)。
在图3所示架构中，UE通过Uu口与(R)AN进行AS(Access Stratum，接入层)连接，交互AS消息 及无线数据传输，UE通过N1口与AMF进行NAS(Non Access Stratum，非接入层)连接，交互NAS消息。AMF是核心网中的移动性管理功能，SMF是核心网中的会话管理功能，AMF在对UE进行移动性管理之外，还负责将会话管理相关消息在UE和SMF之间的转发。PCF是核心网中的策略管理功能，负责制定对UE的移动性管理、会话管理、计费等相关的策略。UPF是核心网中的用户面功能，通过N6接口与外部数据网络进行数据传输，通过N3接口与(R)AN进行数据传输。
需要说明的是，图2、图3中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请实施例对此不作具体限定。图2和图3中包括的各个网元(比如SMF、AF、UPF等)的名称也仅是一个示例，对网元本身的功能不构成限定。在5GS以及未来其它的网络中，上述各个网元也可以是其他的名称，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能采用其他名称，等等，在此进行统一说明，以下不再赘述。此外，应理解，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
在一些实施例中，与策略相关的网元主要是PCF、AMF、SMF、RAN、UE。其中SMF主要是负责与会话相关的策略的执行，AMF主要负责与接入和UE策略相关的策略执行，两个网元(AMF和SMF)上的策略下发、更新全都由PCF来管控。
具体到UE策略，PCF与UE之间通过Container(容器)来监护UE策略相关的信息，包括UE策略的内容、UE策略标识等。所述的Container在上行方向上由UE通过NAS消息发送给AMF，并由AMF继续发送(不感知或不修改)给PCF，下行方向与之相反，由PCF将Container发给AMF，AMF进而通过NAS消息发送给UE。
在介绍本申请技术方案之前，先对本申请涉及的一些背景技术知识进行介绍说明。以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。本申请实施例包括以下内容中的至少部分内容。
1.UE策略配置流程
请参考图4，其示例性示出了一种UE策略配置的流程图。通过3GPP(3rd Generation Partnership Project，第三代合作伙伴计划)定义的UCU(UE Configuration Update，UE配置更新)流程实现UE策略的配置或更新。如图4所示，该UE策略配置的过程如下：
S40，PCF decides to update UE policy(PCF决定更新UE策略)；
S41，Namf_Communication_N1N2Message Transfer(调用AMF的消息传输服务，将用于UE策略更新的消息发送给UE)；
S42，Network Triggered Service Request(网络触发的服务请求)；
S43，Delivery of UE policies(UE策略的传输)；
S44，Result of the delivery of UE policies(UE策略的传输结果)；
S45，Namf_N1MessageNotify(AMF调用消息通知服务，将UE策略的传输结果发送给PCF)。
图4示出的基于UCU实现的UE策略配置或更新流程，可以概述如下：PCF将要更新的策略放在一个容器(container)里，发送给AMF，AMF使用NAS消息转发(如发送)给UE。
为了传输UE策略，在下行NAS和上行NAS消息中引入“UE policy container(UE策略容器)”的原因值，即通过Payload Container(有效载荷容器)增加“UE policy container”原因值。AMF看到该Payload Container中的原因值会执行发送的功能。此“UE policy container”用于携带PCF和UE之间的消息，如下图5所示：
S51，MANAGE UE POLICY COMMAND(PCF向UE发送UE策略管理命令消息)；
步骤S51之后执行步骤S52或S53；
S52，MANAGE UE POLICY COMPLETE(UE向PCF发送UE策略管理完成消息)；
S53，MANAGE UE POLICY COMMAND REJECT(UE向PCF发送UE策略管理拒绝消息)。
此外，如图6所示，S61，UE STATE INDICATION(UE向PCF发送UE状态指示消息)，UE也可以主动向PCF发送UE状态指示消息，以告诉PCF该UE的相关状态信息。
2.UE策略的使用
UE策略包括URSP策略、ANDSP策略等，URSP策略决定了应用数据与PDU会话之间的绑定关系，同时还决定了UE需要建立什么样的PDU会话来满足这种绑定关系。
请参考图7，其示例性示出了一种应用数据流根据URSP策略(或称为URSP规则)绑定到PDU会话的示意图。
示例性地，每一个PDU会话对应一组PDU会话的属性参数。示例性地，不同的应用数据流根据URSP规则绑定到不同的PDU会话上。当然，在一些实施例中，不同的应用数据流根据URSP规则也可以绑定到同一个PDU会话上，在此不作限制。
示例性地，每一个PDU会话具有对应的属性参数，该属性参数包括但不限于以下中的至少一种：S-NSSAI(Single-Network Slice Selection Assistance Information，单个网络切片选择辅助信息)、DNN(Data Network Name，数据网络名字)、PDU Session Type(PDU会话类型)、SSC Mode(Service and Session Continuity Mode，服务和会话连续性模式)。
可选地，UE在发起PDU会话建立请求时，携带上述属性参数。可选地，UE在发起PDU会话建立请求时，有些参数没有携带，那么相应的属性参数由网络侧设备进行填补。示例性地，PDU会话建立请求中包含PDU Sessionid(PDU会话标识)＝1,DNN＝1、PDU Sessiontype＝IPv4时，SMF接收该请求，并填补其他属性参数：S-NSSAI＝1,SSC Mode＝1。示例性地，UE和网络侧保存建立成功的PDU会话中携带的属性参数，包括UE发送的PDU会话建立请求中携带的属性参数以及网络侧填补的属性参数。
请参考表1，其示出了URSP规则中的业务描述符(Traffic Descriptor)和对应的RSD(Route Selection Descriptor，路由选择描述符)列表。请参考表2，其示出了RSD中的具体参数。
可选地，URSP规则中的业务描述符用于描述一种具体的业务，如图7中所示的应用数据流。比如，微博业务用IP@1～9的范围来描述，IMS(IP Multimedia Subsystem，IP多媒体子系统)业务用IMS DNN来描述。可选地，一个业务描述符下面可以有一个或者多个RSD。可选地，RSD中的S-NSSAI的值和DNN的值是一个或多个，RSD中的其他参数值只包含一个值。因此，每一个RSD可以对应一个或者多个参数组合，每个参数组合称为一套PDU会话的特征，业务描述符对应的业务数据可以在RSD的某一个参数组合对应的PDU会话中进行传输。当有业务描述符描述的应用数据流出现时，UE可以根据对应的RSD的Component(组合)值选取一个参数组合，发起PDU会话建立请求。可选地，UE每次发起PDU会话建立请求时，都在请求消息中携带一套会话数据参数，即为某个URSP规则中的RSD表中的参数值组合。
表1 URSP规则中的业务描述符和对应的RSD列表
Figure PCTCN2022078902-appb-000001
Figure PCTCN2022078902-appb-000002
表2路由选择符的参数
Figure PCTCN2022078902-appb-000003
Figure PCTCN2022078902-appb-000004
在一些实施例中，如图7所示，UE基于URSP规则将应用数据流关联到相应的PDU会话上进行传输，机制如下：
当应用层出现数据流时，UE使用URSP策略中的USEP规则来查看该应用数据的特征是否匹配到URSP规则中的某个规则的Traffic Descriptor(业务描述符)上，查看顺序按照URSP规则中即表1中的Rule Precedence(规则优先级)来决定。可选地，UE基于优先级的顺序依次查看匹配情况，当匹配到一个URSP规则时，也就用该URSP规则下的RSD列表进行PDU会话的绑定。
当有URSP规则匹配上时，UE首先查找当前已经建立的PDU会话是否有满足在该匹配的URSP规则下的有效RSD参数，有的话则将匹配的应用数据绑定到该PDU会话上进行传输。否则，按照有效RSD中的Precedence(优先级)顺序来尝试建立PDU会话，这里优先使用优先级高的RSD参数建立PDU会话，如果该RSD中的某个参数为一个或多个取值，则UE选用其中一个与其他参数一起组合建立PDU会话。若该会话建立成功，则UE将该应用数据绑定到该会话进行传输；若该会话建立不成功，则UE基于该RSD中的其他参数组合或者使用次优先级的RSD中的参数组合再次尝试PDU会话建立。
若根据该匹配的URSP规则中的所有参数都不能找到一个合适的PDU会话进行绑定，则UE根据优先级顺序查找次优先的URSP规则中的Traffic Descriptor(业务描述符)业务描述符是否能够匹配该应用数据流特征，当匹配上时，重复之前描述的过程。
整个上述为应用寻找合适的PDU会话的过程我们称之为“evaluation(评估)”，即寻找或建立合适的PDU会话绑定。UE使用的URSP规则中的RSD只有满足以下条件才认为是有效RSD用来执行上述的evaluation(评估)过程：
--如果RSD中有S-NSSAI，S-NSSAI必须属于Allowed NSSAI(非漫游)或者Mapping of Allowed NSSAI(漫游)中的一个；
--如果RSD中有DNN且为LADN(Local Area Data Network，本地数据网络)DNN，则UE必须在该LADN对应的有效区域内；
--如果RSD中有Access Type Prefrence(存取类型介质)并且设置成了Multi-Access(多路接入)，则UE必须支持ATSSS(Access Traffic Steering,Switching,Splitting，接入流量导向，转换，拆分)功能；
--如果RSD中有Timer Window(定时窗口)和Location Criteria(定位标准)，则必须满足要求的时间和地点条件；
否则，UE不会使用该RSD进行数据流的绑定或PDU会话的建立。根据上述evaluation(评估)过程机制，UE可以在发起PDU会话建立被拒绝后，根据RSD参数再次申请PDU会话建立。
如下图8所示，其示例性示出了一种PDU会话建立拒绝和再次尝试的流程图。
S81，UE向SMF发送PDU会话建立请求。
UE在PDU会话建立请求消息中携带PDU会话参数。示例性地，PDU会话参数包括以下的一个或多个：DNN、S-NSSAI、PDU Session Type、SSC Mode、PDU Session ID。
S82，SMF向UE发送PDU会话建立请求回复(拒绝原因值)。
SMF向UE发送PDU会话建立请求回复。如果SMF拒绝该PDU会话建立请求，PDU会话建立请求回复中包括拒绝原因值。
S83，UE根据URSP规则的参数，调整申请的PDU会话参数，再次尝试PDU会话建立。
UE可以根据URSP规则的RSD参数调整参数组合重新发起PDU会话建立。
目前的URSP机制中有如下几个问题：
1)URSP规则中的参数，比如Traffic Descriptor(业务描述符)中的Applicaton Descriptor(应用描述 符)参数，可能无法被终端设备识别。原因比如有些参数需要运营商、终端公司之间的协同，不是运营商单方面可以确定的。当前的evaluation(评估)规则规定：如果终端设备无法识别一个URSP规则里的参数，则会自动忽略掉该URSP规则。但是终端设备不会告知网络侧哪些URSP规则或里面的RSD被忽略了。
问题1：这就造成网络侧下发的某些URSP规则可能永远都不会被终端设备执行，但是网络侧又不知道该情况。
2)当终端设备接收到新的URSP规则时，终端设备会重新evaluate(评估)URSP规则，根据新的URSP规则确定应用数据流与PDU会话的新的绑定关系。但是，终端设备何时evaluate(评估)这个新的规则，以及何时执行新的绑定关系，这两点是终端设备自我实现的。
问题2：网络为终端设备更新了URSP规则后，不能确定何时终端设备会执行新的URSP规则来绑定应用数据流。
3)对于每一个应用数据流，evaluation(评估)规则会最终选择一个URSP规则下的RSD对应的PDU会话进行数据传输。然后，在后续的相当一段时间内不会在改变这种绑定关系。
问题3：终端设备为特定的应用数据流使用的URSP规则以及RSD可能不是优先级最高的，但网络侧并不能确定终端设备为应用使用了哪个URSP规则和RSD。
因此，目前的UE策略(尤其是URSP策略)执行的状态信息只有终端设备自己知道，网络侧无法知晓，也就不确定下发给终端设备的参数是否被使用或按期望执行。因此，需要一种机制让网络侧判断终端设备正在执行UE策略规则。
本申请通过由终端设备向核心网网元发送第一信息，该第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息，使得网络侧设备可以知晓终端设备对于UE策略的使用情况，便于后续的UE策略安排及UE策略更新，有助于提升通信可靠性。
下面，将通过几个实施例对本申请技术方案进行介绍说明。
请参考图9，其示出了本申请一个实施例提供的无线通信方法的流程图。该方法可应用于图1至图3所示的网络架构中。该方法可以包括如下步骤：
步骤910，终端设备向核心网网元发送第一信息，第一信息包括终端设备针对策略规则的使用情况相关的信息。
相应地，核心网网元接收来自终端设备的第一信息。
在一些实施例中，策略规则是由核心网配置的。在一些实施例中，第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息。
策略规则是指由运营商或者其他厂商给终端设备配置的，用于指示终端设备执行相关通信行为的策略或规则。本申请中的策略规则也可以称为UE策略或者UE规则等其他名称，本申请对此不作限定。在一些实施例中，策略规则包括但不限于以下至少一种：URSP、V2XP(Vehicle to Everything Policy、车联网策略)、ProSeP(Proximity Service Policy，邻近服务策略)、ANDSP。
在一些实施例中，终端设备针对策略规则的使用情况，是指终端设备是否识别(recognize)某个或某些策略规则。例如，第一信息用于指示终端设备识别和/或未识别的策略规则。需要说明的是，上述识别/未识别，在一些场景中，也可以理解为认同(identify)/不认同，或支持/不支持，或使用/不使用，本申请对此不作限定。
另外，上述策略规则可以由核心网配置，例如，由核心网网元PCF配置上述策略规则。相应地，终端设备向PCF发送第一信息，该第一信息包括终端设备针对PCF配置的策略规则的使用情况的相关信息。在一些实施例中，终端设备向PCF发送第一信息，可以是终端设备先把第一信息发送给AMF，由AMF将第一信息继续发送给PCF。在一些实施例中，AMF并不感知第一信息，直接发送给PCF。在一些实施例中，AMF不修改第一信息，直接发送给PCF。
在一些实施例中，第一信息包括但不限于以下至少一种：
第一子信息，用于指示识别和/或未识别的策略规则；
第二子信息，用于指示建立PDU会话所使用的策略规则；
第三子信息，用于指示针对一个或多个应用所使用的策略规则；
第四子信息，用于指示针对一个或多个应用所使用的PDU会话和/或网络切片；
第五子信息，用于指示终端设备是否已使用更新的策略规则和/或终端设备使用的策略规则。
对于上述第一子信息，作如下示例性说明：
在一些实施例中，第一子信息用于指示识别的策略规则，如用于指示一个或多个策略规则被识别。例如，第一子信息可以包括用来指示识别的第一指示信息。又例如，第一子信息可以包括至少一个识别的策 略规则的标识信息。
在一些实施例中，第一子信息用于指示未识别的策略规则，如用于指示一个或多个策略规则未被识别。例如，第一子信息可以包括用来指示未识别的第二指示信息。又例如，第一子信息可以包括至少一个未识别的策略规则的标识信息。
在一些实施例中，第一子信息用于指示识别和未识别的策略规则，如用于指示一个或多个策略规则被识别，以及一个或多个策略规则未被识别。例如，第一子信息可以包括用来指示识别的第一指示信息，以及与该第一指示信息对应的至少一个识别的策略规则的标识信息，第一子信息还可以包括用来指示未识别的第二指示信息，以及与该第二指示信息对应的至少一个未识别的策略规则的标识信息。
对于上述第二子信息，作如下示例性说明：
在一些实施例中，第二子信息用于指示建立某一个或多个PDU会话所使用的策略规则。
在一些实施例中，第二子信息可以包括至少一组PDU会话的标识信息和策略规则的标识信息之间的映射关系，每一组映射关系用于指示建立某一个PDU会话所使用的策略规则。
在一些实施例中，第二子信息可以包括至少一个策略规则的标识信息，但不包括PDU会话的标识信息，核心网网元根据该策略规则的标识信息，确定某一个或多个PDU会话是使用该标识信息对应的策略规则所建立的。上述某一个或多个PDU会话可以默认为最后一个建立的PDU会话，或者当前正在传输数据流的PDU会话，或者当前有待传输数据流的PDU会话，或者某一约定业务或数据流所使用的PDU会话等等，本申请对此不作限定。
在一些实施例中，第二子信息可以包括至少一个PDU会话的标识信息，但不包括策略规则的标识信息，核心网网元根据该PDU会话的标识信息，确定某一个或多个策略规则是用于建立该PDU会话的策略规则。上述某一个或多个策略规则可以默认为核心网最近一次配置的策略规则，或者核心网在约定时刻/时段内配置的策略规则等等，本申请对此不作限定。
在一些实施例中，第二子信息也可以仅包括用于指示识别(或者说使用)的第一指示信息，或者包括用于指示未识别(或者说未使用)的第二指示信息，但不包括PDU会话的标识信息，也不包括策略规则的标识信息。核心网网元根据该第一指示信息或者第二指示信息，确定某一个或多个PDU会话使用或未使用某一个或多个策略规则建立。上述某一个或多个PDU会话可以默认为最后一个建立的PDU会话，或者当前正在传输数据流的PDU会话，或者当前有待传输数据流的PDU会话，或者某一约定业务或数据流所使用的PDU会话等等，上述某一个或多个策略规则可以默认为核心网最近一次配置的策略规则，或者核心网在约定时刻/时段内配置的策略规则等等，本申请对此不作限定。
在一些实施例中，第二子信息还用于指示PDU会话与建立该PDU会话所使用的策略规则之间的映射关系。一个PDU会话可以与一个或多个策略规则存在映射关系，一个策略规则也可以与一个或多个PDU会话存在映射关系。示例性地，第二子信息可以包括PDU会话的标识信息与建立该PDU会话所使用的策略规则的标识信息之间的映射关系。
另外，建立PDU会话所使用的策略规则，可以包括URSP，或者也可以包括其他策略规则，本申请对此不作限定。
对于上述第三子信息，作如下示例性说明：
在一些实施例中，第三子信息可以包括至少一组应用的标识信息和策略规则的标识信息之间的映射关系，每一组映射关系用于指示针对某一个应用所使用的策略规则。
在一些实施例中，第三子信息可以包括至少一个策略规则的标识信息，但不包括应用的标识信息，核心网网元根据该策略规则的标识信息，确定某一个或多个应用使用该标识信息对应的策略规则，例如确定某一个或多个应用的数据流是使用该标识信息对应的策略规则所建立的PDU会话传输的。上述某一个或多个应用可以默认为当前正在传输数据流的应用，或者当前有待传输数据流的应用，或者某一个或多个约定的应用等等，本申请对此不作限定。
在一些实施例中，第三子信息可以包括至少一个应用的标识信息，但不包括策略规则的标识信息，核心网网元根据该应用的标识信息，确定某一个或多个策略规则被该标识信息指示的应用所使用。上述某一个或多个策略规则可以默认为核心网最近一次配置的策略规则，或者核心网在约定时刻/时段内配置的策略规则等等，本申请对此不作限定。
在一些实施例中，第三子信息也可以仅包括用于指示识别(或者说使用)的第一指示信息，或者包括用于指示未识别(或者说未使用)的第二指示信息，但不包括应用的标识信息，也不包括策略规则的标识信息。核心网网元根据该第一指示信息或者第二指示信息，确定某一个或多个应用使用或未使用某一个或多个策略规则。上述某一个或多个应用可以默认为当前正在传输数据流的应用，或者当前有待传输数据流的应用，或者某一个或多个约定的应用等等，上述某一个或多个策略规则可以默认为核心网最近一次配置的策略规则，或者核心网在约定时刻/时段内配置的策略规则等等，本申请对此不作限定。
在一些实施例中，第三子信息还用于指示针对应用在不同时刻或不同时段所使用的策略规则。对于同一个应用来说，其在不同时刻或不同时段可以使用不同的策略规则，也可以使用相同的策略规则。可选地，第三子信息可以包括至少一组时刻/时段与策略规则之间的映射关系，每一组映射关系用于指示某一应用在某一时刻/时段所使用的策略规则。
对于上述第四子信息，作如下示例性说明：
在一些实施例中，第四子信息可以包括至少一组应用的标识信息和PDU会话和/或网络切片的标识信息之间的映射关系，每一组映射关系用于指示针对某一个应用所使用的PDU会话和/或网络切片。
在一些实施例中，第四子信息可以包括至少一个PDU会话和/或网络切片的标识信息，但不包括应用的标识信息，核心网网元根据该PDU会话和/或网络切片的标识信息，确定某一个或多个应用使用该标识信息对应的PDU会话和/或网络切片，例如确定某一个或多个应用的数据流是使用该标识信息对应的PDU会话和/或网络切片传输的。上述某一个或多个应用可以默认为当前正在传输数据流的应用，或者当前有待传输数据流的应用，或者某一个或多个约定的应用等等，本申请对此不作限定。
在一些实施例中，第四子信息可以包括至少一个应用的标识信息，但不包括PDU会话和/或网络切片的标识信息，核心网网元根据该应用的标识信息，确定某一个或多个PDU会话和/或网络切片被该标识信息指示的应用所使用。上述某一个或多个PDU会话和/或网络切片可以默认为一个或多个约定的PDU会话和/或网络切片，如最后一个建立的PDU会话和/或网络切片，或者当前正在传输数据流的PDU会话和/或网络切片，或者当前有待传输数据流的PDU会话和/或网络切片等等，本申请对此不作限定。
在一些实施例中，第四子信息也可以仅包括用于指示识别(或者说使用)的第一指示信息，或者包括用于指示未识别(或者说未使用)的第二指示信息，但不包括应用的标识信息，也不包括PDU会话和/或网络切片的标识信息。核心网网元根据该第一指示信息或者第二指示信息，确定某一个或多个应用使用或未使用某一个或多个PDU会话和/或网络切片。上述某一个或多个应用可以默认为当前正在传输数据流的应用，或者当前有待传输数据流的应用，或者某一个或多个约定的应用等等；上述某一个或多个PDU会话和/或网络切片可以默认为一个或多个约定的PDU会话和/或网络切片，如最后一个建立的PDU会话和/或网络切片，或者当前正在传输数据流的PDU会话和/或网络切片，或者当前有待传输数据流的PDU会话和/或网络切片等等，本申请对此不作限定。
对于上述第五子信息，作如下示例性说明：
在一些实施例中，第五子信息用于指示终端设备是否已使用更新的策略规则。例如，第五子信息用于指示终端设备已使用更新的策略规则，或者第五子信息用于指示终端设备未使用更新的策略规则。上述更新的策略规则可以是核心网网元通过下行消息进行更新的，如UCU消息或者其他消息，本申请对此不作限定。在一些实施例中，第五子信息可以包括一个比特位的指示信息，用于指示终端设备是否已使用更新的策略规则。
在一些实施例中，第五子信息用于指示终端设备使用的策略规则，需要说明的是，此处的“使用”可以是指“已使用”，也可以是指“正在使用”。例如，第五子信息用于指示终端设备已使用的策略规则，或者，第五子信息用于指示终端设备正在使用的策略规则。在一些实施例中，第五子信息可以包括终端设备使用的策略规则的标识信息，以此来指示终端设备使用的策略规则。
在一些实施例中，第五子信息用于指示终端设备是否已使用更新的策略规则，以及用于指示终端设备使用的策略规则。同样的，此处的“使用”可以是指“已使用”，也可以是指“正在使用”。也即，在此示例中，第五子信息兼具上述2种功能。
在一些实施例中，网络切片可以有不同的标识(如S-NSSAI，NSI ID(Network Slice Instances ID，网络切片实例的标识)等)，以S-NSSAI标识为例，不同的网络切片具有不同的S-NSSAI，终端设备和核心网网元能够根据S-NSSAI区分不同的网络切片。
另外，需要说明的是，由于第四子信息用于指示针对一个或多个应用所使用的PDU会话和/或网络切片，而PDU会话和/或网络切片与策略规则之间可以存在映射关系，那么也就相当于指示了针对一个或多个应用所使用的策略规则。
在一些实施例中，策略规则的指代方式包括以下至少一种：采用策略规则的Rule ID(规则标识)进行指代；采用策略规则的一个或多个参数进行指代。也就是说，上文所说的策略规则的标识信息，可以用策略规则的Rule ID(或者简称为ID)来表示，也可以用策略规则的一个或多个参数来表示。
采用策略规则的Rule ID进行指代是指以Rule ID唯一指代策略规则。在一些实施例中，终端设备所采用的策略规则是URSP规则，则以URSPRule ID(URSP规则ID)来指代URSP规则。在一些实施例中，还可以进一步采用RSD ID来指代RSD。例如采用URSP Rule ID和RSD ID，来指代某个URSP规则和该URSP规则下的RSD。
采用策略规则的参数进行指代是指以策略规则的一个或多个参数来唯一指代策略规则。在一些实施例 中，终端设备所采用的策略规则是URSP规则，则以URSP规则中的Traffic descriptor(业务描述符)或Rule Precedence(规则优先级)来指代URSP规则。在一些实施例中，还可以采用RSD的Precedence(RSD优先级)或Route selection components(路由选择组分，也即路由选择参数)来指代RSD。例如采用URSP规则中的Traffic descriptor/Rule Precedence和RSD的Precedence/Route selection components来指代某个URSP规则和该URSP规则下的RSD。
在一些实施例中，策略规则为URSP的情况下，第一信息所指示的策略规则包括URSP规则和/或该URSP规则下的至少一个RSD。
本申请实施例提供的技术方案，通过终端设备向核心网网元发送第一信息，该第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息，使得核心网网元可以知晓终端设备对于策略规则的使用情况，便于后续策略规则的配置及更新，有助于提升通信可靠性。
请参考图10，其示出了本申请另一个实施例提供的无线通信方法的流程图。该方法可应用于图1至图3所示的网络架构中。该方法可以包括如下步骤(1010～1020)中的至少一个步骤：
步骤1010，核心网网元向终端设备发送下行消息。
在一些实施例中，下行消息中包括核心网为终端设备配置的策略规则。例如，下行消息中包括核心网为终端设备配置的URSP规则。当然，此处仅以URSP规则进行举例性说明，还可以是上文介绍的其他规则策略，本申请对此不作限定。另外，有关策略规则的介绍说明可参见上下文其他实施例中的内容，本实施例对此不再赘述。
在一些实施例中，核心网网元是PCF，PCF想要给终端设备发送下行消息，需要先给AMF发送下行消息，由AMF将下行消息转发给终端设备。在一些实施例中，AMF不感知/不修改下行消息，直接将PCF发来的下行消息发送给终端设备。
在一些实施例中，下行消息为UCU消息。在一些实施例中，UCU消息是指由核心网网元发送给终端设备用于指示终端设备进行配置更新的消息。在一些实施例中，核心网网元是PCF，PCF将UCU消息放在第三容器中，通过第三容器将UCU消息发送给AMF，经过AMF发送给终端设备。
相应地，终端设备接收核心网网元发送的下行消息。
步骤1020，终端设备向核心网网元发送下行消息对应的回复消息，该回复消息中包括第一信息，该第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息。
有关第一信息的介绍说明可参见上下文其他实施例中的内容，本实施例对此不再赘述。
相应地，核心网网元接收来自终端设备的回复消息。
在一些实施例中，终端设备在接收到下行消息之后，对下行消息中包含的策略规则进行评估，确定识别和/或未识别的策略规则；终端设备根据该识别和/或未识别的策略规则，生成第一信息。
例如，下行消息中包括核心网(如PCF)为终端设备配置的一个策略规则，假设为策略规则1，假设终端设备对该策略规则1进行评估，确定可识别(或认同，或支持，或使用)该策略规则1，那么终端设备向核心网网元发送的回复消息中携带的第一信息，可以包括用于指示识别(或认同，或支持，或使用)的第一指示信息。可选地，第一信息中还可以包括该识别(或认同，或支持，或使用)的策略规则1的标识信息。
例如，下行消息中包括核心网(如PCF)为终端设备配置的一个策略规则，假设为策略规则1，假设终端设备对该策略规则1进行评估，确定未识别(或不认同，或不支持，或不使用)该策略规则1，那么终端设备向核心网网元发送的回复消息中携带的第一信息，可以包括用于指示未识别(或不认同，或不支持，或不使用)的第二指示信息。可选地，第一信息中还可以包括该未识别(或不认同，或不支持，或不使用)的策略规则1的标识信息。
例如，下行消息中包括核心网(如PCF)为终端设备配置的多个策略规则，假设包括策略规则1和策略规则2，假设终端设备对该策略规则1和2分别进行评估，确定可识别(或认同，或支持，或使用)该策略规则1，未识别(或不认同，或不支持，或不使用)该策略规则2，那么终端设备向核心网网元发送的回复消息中携带的第一信息，可以用于指示终端设备可识别(或认同，或支持，或使用)该策略规则1，也可以用于指示终端设备未识别(或不认同，或不支持，或不使用)该策略规则2，还可以用于指示终端设备可识别(或认同，或支持，或使用)该策略规则1且未识别(或不认同，或不支持，或不使用)该策略规则2。
在一些实施例中，回复消息包含在第一容器中。终端设备将回复消息放在第一容器中，通过第一容器将回复消息发送给核心网网元。在一些实施例中，核心网网元是PCF，终端设备通过第一容器将回复消息先发送给AMF，由AMF不感知/不修改地将回复消息发送给PCF。
在一些实施例中，第一信息复用回复消息中的已有字段。回复消息中的已有字段是指回复消息中已经 定义的字段，通过复用该已有字段承载第一信息，可以不对回复消息的格式或字段进行修改。
在一些实施例中，第一信息使用回复消息中的新增字段。回复消息中的新增字段是指为了在回复消息中携带第一信息，在回复消息中新增一个字段来承载该第一信息，这种方式仅需对回复消息的改动也较小。
在一些实施例中，使用新定义格式的回复消息传输第一信息。上述两种方式都是使用回复消息的原有格式来承载第一信息，这种方式是给回复消息新定义一种格式，通过该新定义的格式来传输第一信息。这种设计方式相对于前面两种更加灵活，但是需要对回复消息的格式进行重新定义。
下面，以下行消息为UCU消息，终端设备在UCU消息对应的回复消息中传输上述第一信息为例，对本申请技术方案进行介绍说明。例如，终端设备在UCU消息对应的回复消息中，添加第一信息，该第一信息用于指示终端设备能够识别(或认同，或支持，或使用)的URSP规则。
核心网网元(如PCF)向终端设备发送用于UE策略配置/更新的UCU消息，该UCU消息中包括核心网网元配置的URSP规则。终端设备接收到上述UCU消息之后，对该UCU消息中包含的URSP规则进行评估，确定是否支持该URSP规则中的参数。如果该URSP规则中的一个或多个参数无法支持，那么终端设备确定不支持(或称为未识别，或不认同，或不使用)该URSP规则。或者，如果该URSP规则中的某个RSD中的一个或多个参数无法支持，那么终端设备确定不支持(或称为未识别，或不认同，或不使用)该URSP规则下的该RSD，但该URSP规则下的其他RSD还是可以支持的(也可以对于该URSP规则下的全部RSD都认为不支持)。
终端设备在UCU消息对应的回复消息中，可以携带第一信息用于指示该终端设备支持(和/或不支持)的URSP规则和/或RSD。该第一信息也可以称为UE策略执行信息，或URSP规则执行信息，或者其他名称，本申请对此不作限定。
由于通过UCU消息向终端设备下发策略规则时，可以分为多个策略分段(Policy Section)进行下发，每个策略分段对应一个策略分段码(Policy Section Code)。因此，终端设备可以在回复消息中，基于每个策略分段中的哪个URSP规则和/或其下面的哪个RSD是否支持(或识别，或认同，或使用)进行回复。
请参考图11至图15，其示例性示出了UCU消息对应的回复消息的格式示意图。图11至图15所示的消息格式呈逐层嵌套关系。
具体来讲，图11是UE policy section management result information element(UE策略分段管理结果信息元素)的格式示意图，从图11可以看出，每个策略分段的管理结果信息元素包括UE policy section management result IEI(UE策略分段管理结果信息元素标识符)、Length of UE policy section management result contents(UE策略分段管理结果内容的长度)和UE policy section management result contents(UE策略分段管理结果内容)。
图12是UE policy section management result contents(UE策略分段管理结果内容)的格式示意图，从图12可以看出，UE policy section management result contents可以包括多个UE policy section management subresult(UE策略分段管理子结果)，例如PLMN 1、PLMN 2、…、PLMN N分别对应的UE policy section management subresult。
图13是UE policy section management subresult(UE策略分段管理子结果)的格式示意图，从图13可以看出，UE policy section management subresult可以包括Number of results(结果数量)、若干个MCC digit(国家码代码位)、若干个MNC digit(网络运营商代码位)以及UE policy section management subresult contents(UE策略分段管理子结果内容)。
图14是UE policy section management subresult contents(UE策略分段管理子结果内容)的格式示意图，从图14可以看出，UE policy section management subresult contents可以包括多个Result(结果)，如Result 1(结果1)、Result 2(结果2)、…、Result N(结果N)等。
图15是Result(结果)的格式示意图，从图15可以看出，Result可以包括UPSC(UPSC用于指示一个PLMN下的UE策略分成的不同部分)、Failed instruction order(指令失效命令)、Cause(原因值)等字段。
在一个示例中，终端设备利用UCU消息对应的回复消息中的已有字段，承载上述第一信息。如图15所示，对于方案1：终端设备可以复用Cause(原因值)字段承载上述第一信息，指示一个策略分段中的哪个URSP规则和/或其下面的哪个RSD是否支持(或识别，或认同，或使用)。
在另一个示例中，终端设备利用UCU消息对应的回复消息中的新增字段，承载上述第一信息。如图15所示，对于方案2：终端设备添加一个新的字段承载上述第一信息，指示一个策略分段中的哪个URSP规则和/或其下面的哪个RSD是否支持(或识别，或认同，或使用)。
在另一个示例中，终端设备使用新定义格式的回复消息传输第一信息。例如，如图16所示，终端设备在UCU消息对应的回复消息中不考虑policy section(策略分段)的问题，新定义一个表格(table)表示该终端设备支持(或不支持)的URSP规则和/或其下面的RSD。例如，该表格中可以包括多个PLMN分 别对应的条目，每一个条目用于指示一个PLMN下支持(或不支持)的URSP规则和/或其下面的RSD。
在本实施例中，通过在下行消息(如UCU消息)对应的回复消息中，携带用于指示终端设备针对策略规则的使用情况的第一信息，使得核心网网元可以知晓终端设备对于策略规则的使用情况，便于后续策略规则的配置及更新，有助于提升通信可靠性。
请参考图17，其示出了本申请另一个实施例提供的无线通信方法的流程图。该方法可应用于图1至图3所示的网络架构中。该方法可以包括如下步骤：
步骤1710，终端设备向核心网网元发送上行消息，该上行消息中包括第一信息，该第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息。
相应地，核心网网元接收来自终端设备的上行消息。有关第一信息的介绍说明可参见上下文其他实施例中的内容，在此不再赘述。
在此实施例中，终端设备可以主动向核心网网元发送上行消息，上报其针对核心网配置的策略规则的使用情况相关的信息。
在一些实施例中，上行消息为UE状态指示消息，即UE State Indication消息(或称为UE STATE INDICATION消息)。
在一些实施例中，终端设备向核心网网元发送注册请求消息，注册请求消息中包含第二容器，该第二容器中包含上行消息(如UE State Indication消息)。在一些实施例中，核心网网元是PCF，终端设备向AMF发送注册请求消息，该注册请求消息中包含第二容器，包含第一信息的上行消息承载在第二容器中，AMF收到该注册请求消息之后，将第二容器中的信息转发给PCF。
在一些实施例中，注册请求消息包括但不限于以下至少一种：初始注册请求消息、周期性注册请求消息、位置更新的注册请求消息。初始注册请求消息是指终端设备初始开机时向核心网网元发送的注册请求消息。周期性注册请求消息是指终端设备向核心网网元周期性发送的注册请求消息。位置更新的注册请求消息是指在终端设备发生位置更新时向核心网网元发送的注册请求消息。
在一些实施例中，当第一信息发生变化时，终端设备向核心网网元发送包含变化后的第一信息的注册请求消息。例如，当第一信息发生变化时，终端设备主动向核心网网元发送注册请求消息，该注册请求消息中包含变化后的第一信息，从而实现将变化后的第一信息及时地上报给核心网网元。
在一些实施例中，当第一信息发生变化时，终端设备在因其他原因触发向核心网网元发送的注册请求消息中携带变化后的第一信息。可选地，其他原因包括但不限于现有的触发注册请求消息的原因，比如初始开机、周期性定时器到期、移出注册区、终端能力更新等条件下发起的注册请求消息。
在一些实施例中，终端设备使用上行消息中的新增字段承载第一信息。例如，以上行消息为UE状态指示消息为例，可以在该UE状态指示消息中新增一个字段，用于承载第一信息。当然，在一些其他实施例中，也可以复用上行消息中的已有字段承载第一信息，或者上行消息还可以是除UE状态指示消息之外的其他上行消息，本申请对此不作限定。
下面，以上行消息为UE状态指示消息，终端设备在UE状态指示消息中传输上述第一信息为例，对本申请技术方案进行介绍说明。下述表3示例性示出了UE状态指示消息(UE STATE INDICATION消息)的消息内容的示意图。
表3 UE STATE INDICATION message content(UE状态指示消息内容)
Figure PCTCN2022078902-appb-000005
Figure PCTCN2022078902-appb-000006
在一些实施例中，如图18所示，其示例性示出了终端设备(图中以UE示出)向核心网网元(图中以PCF示出)发送注册请求消息的流程图。在该注册请求消息中，可以携带上文介绍的第一信息。如图18所示，该过程可以包括如下几个步骤：
步骤1810，UE向(R)AN发送Registration Request(注册请求)消息；
步骤1820，(R)AN向AMF发送Registration Request消息；
步骤1830，AMF与PCF间进行AM Policy Association Establishment/Modification(AM策略关联建立/修改)流程；
步骤1840，AMF向UE发送Registration Accept(注册接受)消息。
在一些实施例中，Registration Request消息中包含容器(即上文实施例中介绍的“第二容器”)，包含第一信息的UE State Indication消息承载在该容器中，AMF收到该Registration Request消息之后，在AMF与PCF进行AM策略关联建立/修改的过程中，AMF将容器中的信息转发给PCF，从而实现了在终端注册请求过程中向网络侧上报第一信息。另外，该Registration Request消息可以是初始Registration Request消息、周期性Registration Request消息、位置更新的Registration Request消息等，本申请对此不作限定。
在一些实施例中，AMF调用Npcf_UEPolicyControl Service服务，通过该Npcf_UEPolicyControl Service服务将容器中的信息转发给PCF。
在一些实施例中，AMF向UE发送的注册请求对应的回复消息，可以指示注册完成(如Registration Accept消息)，也可以指示注册拒绝，本申请对此不作限定。
在本实施例中，通过在上行消息(如UE状态指示消息)中，携带用于指示终端设备针对策略规则的使用情况的第一信息，实现了策略规则使用情况的主动上报，使得核心网网元可以知晓终端设备对于策略规则的使用情况，便于后续策略规则的配置及更新，有助于提升通信可靠性。
请参考图19，其示出了本申请另一个实施例提供的无线通信方法的流程图。该方法可应用于图1至图3所示的网络架构中。该方法可以包括如下步骤：
步骤1910，终端设备向核心网网元发送PDU会话建立/修改请求，该PDU会话建立/修改请求中包括第一信息，该第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息。
相应地，核心网网元接收来自终端设备的PDU会话建立/修改请求。有关第一信息的介绍说明可参见上下文其他实施例中的内容，在此不再赘述。
在此实施例中，终端设备可以在PDU会话建立请求和/或PDU会话建立请求中，携带需要上报给核心网的第一信息。有关PDU会话建立/修改的介绍说明可参见上下文其他实施例中的内容，在此不再赘述。
在一些实施例中，终端设备向核心网网元发送PDU会话建立/修改请求，PDU会话建立/修改请求中除了包括PDU会话参数之外，还包括第一信息。在一些实施例中，终端设备向SMF发送PDU会话建立/修改请求，SMF收到该PDU会话建立/修改请求之后，SMF向终端设备发送PDU会话建立/修改请求对应的回复消息。如果SMF拒绝该PDU会话建立/修改请求，PDU会话建立/修改请求对应的回复消息中包括拒绝原因值。在一些实施例中，终端设备可以根据URSP规则的RSD参数调整参数组合重新发起PDU会话修改请求，SMF收到该PDU会话修改请求之后，作出相应回复。另外，在PDU会话建立/修改请求中包括第一信息的情况下，SMF在接收到PDU会话建立/修改请求之后，可以从中获取第一信息，并将第一信息发送给PCF。
在一些实施例中，当第一信息发生变化时，终端设备向核心网网元发送包含变化后的第一信息的PDU会话建立/修改请求。例如，当第一信息发生变化时，终端设备主动向核心网网元发送PDU会话建立/修改请求，该PDU会话建立/修改请求中包含变化后的第一信息，从而实现将变化后的第一信息及时地上报给核心网网元。
在一些实施例中，当第一信息发生变化时，终端设备在因其他原因触发向核心网网元发送的PDU会话建立/修改请求中携带变化后的第一信息。可选地，其他原因包括但不限于现有的触发PDU会话建立/ 修改请求的原因，比如满足PDU会话的建立条件时、满足PDU会话的修改条件时，等等，本申请对此不作限定。
在一些实施例中，终端设备使用PDU会话建立/修改请求中的新增字段承载第一信息。例如，可以在该PDU会话建立/修改请求中新增一个字段，用于承载第一信息。当然，在一些其他实施例中，也可以复用PDU会话建立/修改请求中的已有字段承载第一信息，本申请对此不作限定。
在本实施例中，通过在PDU会话建立/修改请求中，携带用于指示终端设备针对策略规则的使用情况的第一信息，实现了策略规则使用情况的上报，使得核心网网元可以知晓终端设备对于策略规则的使用情况，便于后续策略规则的配置及更新，有助于提升通信可靠性。
在上文提供的图10、图17和图19所示的实施例中，分别介绍了第一信息的几种不同上报方式，包括基于UCU过程上报第一信息、基于终端注册过程上报第一信息、基于PDU会话建立/修改过程上报第一信息等。可以理解的是，终端设备还可以在其他上行消息，或者下行消息对应的回复消息中，携带第一信息，以实现向核心网上报第一信息。这都应当在本申请的保护范围之内，本申请实施例将不对此做一一举例。
在一些实施例中，终端设备在向核心网网元发送第一信息之前，还可以存在如下示例性实施例所介绍的过程。
在一些实施例中，终端设备向核心网网元发送第一指示，相应地，核心网网元接收终端设备发送的第一指示，该第一指示用于指示终端设备支持上报第一信息和/或第一信息中的至少一个子信息。在此示例中，核心网网元可以是PCF。
上述第一指示也可以看作是终端设备的能力指示，用于向核心网告知该终端设备是否支持(或请求，或允许，或要求，即该参数可以使网络侧知道终端设备可以上报第一信息)上报第一信息，和/或，用于向核心网告知该终端设备支持(或请求，或允许，或要求，即该参数可以使终端设备知道需要上报第一信息)上报第一信息中的哪个或哪些子信息。例如，第一指示用于指示终端设备支持上报第一信息，且支持上报第一信息中的第一子信息和第二子信息。有关第一信息以及该第一信息中各项子信息的介绍说明，可参见上文实施例，此处不再赘述。
核心网网元在接收到上述第一指示之后，可以决定是否允许终端设备上报第一信息，和/或，允许或不允许终端设备上报第一信息中的哪个或哪些子信息，然后将上述决定结果发送给终端设备，以便于终端设备按照网络侧的要求进行第一信息的上报。
在一些实施例中，核心网网元向终端设备发送第二指示，终端设备接收来自核心网网元的第二指示，该第二指示用于指示核心网网元支持终端设备上报第一信息和/或第一信息中的至少一个子信息。在此示例中，核心网网元可以是PCF。
上述第二指示也可以看作是网络侧的需求指示，用于向终端设备告知该核心网是否支持(或允许，或请求)上报第一信息，和/或，用于向终端设备告知该核心网支持(或允许，或请求)上报第一信息中的哪个或哪些子信息。例如，第二指示用于指示核心网支持上报第一信息，且支持上报第一信息中的第一子信息和第三子信息。有关第一信息以及该第一信息中各项子信息的介绍说明，可参见上文实施例，此处不再赘述。
终端设备在接收到上述第二指示之后，可以决定是否向核心网上报第一信息，和/或，上报第一信息中的哪个或哪些子信息，以便于终端设备按照网络侧的要求进行第一信息的上报。
上述一个示例中，介绍了终端设备向核心网网元发送第一指示，后续终端设备可以根据该第一指示向核心网网元上报第一信息。例如，第一指示用于指示终端设备支持上报第一信息且支持上报第一信息中的第一子信息和第二子信息，那么终端设备向核心网网元上报的第一信息中包括第一子信息和第二子信息。相应地，核心网网元接收到该第一指示之后，便可根据该第一指示确定终端设备是否会上报第一信息，以及在上报第一信息的情况下，会上报该第一信息中的哪个或哪些子信息，从而准确接收第一信息。需要说明的是，在此示例中，终端设备向核心网网元发送了第一指示，但是核心网网元不需要向终端设备发送第二指示。
另一个示例中，介绍了核心网网元向终端设备发送第二指示，后续终端设备可以根据该第二指示向核心网网元上报第一信息。例如，如果第二指示用于指示核心网网元支持终端设备上报第一信息，那么终端设备向核心网网元上报第一信息；如果第二指示用于指示核心网网元不支持终端设备上报第一信息，那么终端设备不向核心网网元上报第一信息。又例如，如果第二指示用于指示核心网网元支持终端设备上报第一信息中的某一种或几种子信息，那么终端设备向核心网网元上报的第一信息中，携带上述核心网网元支持的子信息，核心网网元不支持上报的子信息终端设备可以不用上报，从而避免不必要的信息传输。需要说明的是，在此示例中，核心网网元向终端设备发送了第二指示，但是终端设备不需要向核心网网元发送 第一指示。
另外，对于上述终端设备发送第一指示的过程和核心网网元发送第二指示的过程，这两个过程可以择其一执行，也可以两者都执行。在两者都执行的情况下，可以实现成为终端设备和核心网之间的一个协商过程。
在一些实施例中，终端设备向核心网网元发送第一指示，该第一指示用于指示终端设备支持上报第一信息和/或第一信息中的至少一个子信息；以及，核心网网元向终端设备发送第二指示，该第二指示用于指示核心网网元支持终端设备上报第一信息和/或第一信息中的至少一个子信息。也即，在该协商过程中，终端设备向核心网网元发送了第一指示，核心网网元向终端设备发送了第二指示。关于第一指示和第二指示的发送先后顺序，本申请对此不作限定，可以先由终端设备向核心网网元发送第一指示，然后核心网网元向终端设备发送第二指示；或者，也可以先由核心网网元向终端设备发送第二指示，然后终端设备向核心网网元发送第一指示；或者，第一指示和第二指示的发送过程同时执行，本申请对此不作限定。
例如，第一指示用于指示终端设备支持上报第一信息，且支持上报第一信息中的第一子信息和第二子信息，第二指示用于指示核心网支持上报第一信息，且支持上报第一信息中的第一子信息和第三子信息。那么基于上述协商过程，终端设备可以向核心网网元上报第一信息，且上报第一子信息，第二子信息和第三子信息不上报(即便在有的情况下也不上报)，从而可以实现网络侧对终端上报信息的控制，且避免不必要的信息传输，节省传输资源。而且，通过该协商过程，使得终端设备和核心网之间关于第一信息是否上报，以及上报第一信息中的哪个或哪些子信息达成一致，提升了终端设备和核心网之间的协同性和一致性。
另外，上述第一指示和第二指示的发送可以发生在UCU过程中，也可以发生在终端注册过程中。当然，在一些其他实施例中，上述第一指示和第二指示也可以采用专用消息发送，或者携带在其他已有消息中发送，本申请对此不作限定。
在一些实施例中，在基于UCU过程上报第一信息的情况下，核心网网元向终端设备发送的UCU消息中包括第二指示，和/或，UCU消息对应的回复消息中包括第一指示。
另外，如果终端设备在UCU消息对应的回复消息中发送第一指示，那么在确定要上报第一信息的情况下，第一信息可以携带在该UCU消息对应的回复消息中，也可以在发送UCU消息对应的回复消息之后再发送第一信息，本申请对此不作限定。
在一些实施例中，在基于终端注册过程上报第一信息的情况下，终端设备向核心网网元发送的注册请求消息中包括第一指示，和/或，注册请求消息对应的回复消息中包括第二指示。
另外，如果终端设备在注册请求消息中发送第一指示，那么在确定要上报第一信息的情况下，第一信息可以携带在该注册请求消息中，也可以在接收到注册请求消息对应的回复消息之后再发送第一信息，本申请对此不作限定。
在一些实施例中，在基于PDU会话建立/修改过程上报第一信息的情况下，终端设备向核心网网元发送的PDU会话建立/修改请求中包括第一指示，和/或，PDU会话建立/修改请求对应的回复消息中包括第二指示。
另外，如果终端设备在PDU会话建立/修改请求中发送第一指示，那么在确定要上报第一信息的情况下，第一信息可以携带在该PDU会话建立/修改请求中，也可以在接收到PDU会话建立/修改请求对应的回复消息之后再发送第一信息，本申请对此不作限定。在本申请实施例中，通过上述第一指示和/或第二指示，实现了网络侧对终端上报信息的控制，且避免不必要的信息传输，节省传输资源。
下述为本申请装置实施例，可以用于执行本申请方法实施例。对于本申请装置实施例中未披露的细节，请参照本申请方法实施例。
请参考图20，其示出了本申请一个实施例提供的无线通信装置的框图。该装置可以实现成为终端设备，或者，实现成为终端设备中的一部分。如图20所示，该装置2000可以包括：发送模块2010。
发送模块2010，用于向核心网网元发送第一信息，所述第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息。
在一些实施例中，所述第一信息包括以下至少一种：
第一子信息，用于指示识别和/或未识别的策略规则；
第二子信息，用于指示建立PDU会话所使用的策略规则；
第三子信息，用于指示针对一个或多个应用所使用的策略规则；
第四子信息，用于指示针对一个或多个应用所使用的PDU会话和/或网络切片；
第五子信息，用于指示所述终端设备是否已使用更新的策略规则和/或所述终端设备使用的策略规则。
在一些实施例中，所述第二子信息还用于指示所述PDU会话与建立所述PDU会话所使用的策略规则 之间的映射关系。
在一些实施例中，所述第三子信息还用于指示针对所述应用在不同时刻或不同时段所使用的策略规则。
在一些实施例中，所述网络切片以S-NSSAI标识。
在一些实施例中，所述发送模块2010，用于在接收到所述核心网网元发送的下行消息之后，向所述核心网网元发送所述下行消息对应的回复消息，所述回复消息中包括所述第一信息。
在一些实施例中，如图20所示，所述装置2000还包括处理模块2020，用于在接收到所述下行消息之后，对所述下行消息中包含的策略规则进行评估，确定识别和/或未识别的策略规则；根据所述识别和/或未识别的策略规则，生成所述第一信息。
在一些实施例中，所述回复消息包含在第一容器中。
在一些实施例中，所述下行消息为UCU消息。
在一些实施例中，所述第一信息复用所述回复消息中的已有字段，或者，所述第一信息使用所述回复消息中的新增字段。
在一些实施例中，使用新定义格式的所述回复消息传输所述第一信息。
在一些实施例中，所述发送模块2010，用于向所述核心网网元发送上行消息，所述上行消息中包括所述第一信息。
在一些实施例中，所述发送模块2010，用于向所述核心网网元发送注册请求消息，所述注册请求消息中包含第二容器，所述第二容器中包含所述上行消息。
在一些实施例中，所述注册请求消息包括以下至少一种：初始注册请求消息、周期性注册请求消息、位置更新的注册请求消息。
在一些实施例中，所述发送模块2010，还用于当所述第一信息发生变化时，向所述核心网网元发送包含变化后的第一信息的注册请求消息，或者因其他原因触发向所述核心网网元发送的注册请求消息中携带所述变化后的第一信息。
在一些实施例中，所述上行消息为UE状态指示消息。
在一些实施例中，使用所述上行消息中的新增字段承载所述第一信息。
在一些实施例中，所述发送模块2010，用于向所述核心网网元发送PDU会话建立/修改请求，所述PDU会话建立/修改请求中包括所述第一信息。
在一些实施例中，所述发送模块2010，用于向所述核心网网元发送第一指示，所述第一指示用于指示所述终端设备支持上报所述第一信息和/或所述第一信息中的至少一个子信息；
和/或，所述装置2000还包括接收模块(图20中未示出)，用于接收来自所述核心网网元的第二指示，所述第二指示用于指示所述核心网网元支持所述终端设备上报所述第一信息和/或所述第一信息中的至少一个子信息。
在一些实施例中，在基于UCU过程上报所述第一信息的情况下，所述核心网网元向所述终端设备发送的UCU消息中包括所述第二指示，和/或，所述UCU消息对应的回复消息中包括所述第一指示。
在一些实施例中，在基于终端注册过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的注册请求消息中包括所述第一指示，和/或，所述注册请求消息对应的回复消息中包括所述第二指示。
在一些实施例中，在基于PDU会话建立/修改过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的PDU会话建立/修改请求中包括所述第一指示，和/或，所述PDU会话建立/修改请求对应的回复消息中包括所述第二指示。
在一些实施例中，所述策略规则的指代方式包括以下至少一种：
采用所述策略规则的Rule ID进行指代；
采用所述策略规则的一个或多个参数进行指代。
在一些实施例中，在所述策略规则是UE URSP的情况下，采用所述策略规则的一个或多个参数进行指代，包括：采用所述URSP规则的Traffic descriptor和/或Rule Precedence，指代所述URSP规则；和/或，采用所述URSP规则下的RSD的Precedence和/或Route selection components，指代所述URSP规则下的RSD。
在一些实施例中，所述策略规则包括以下至少一种：URSP、V2XP、ProSeP、ANDSP。
在一些实施例中，在所述策略规则为URSP的情况下，所述第一信息所指示的策略规则包括URSP规则和/或所述URSP规则下的至少一个RSD。
请参考图21，其示出了本申请另一个实施例提供的无线通信装置的框图。该装置可以实现成为核心网网元，或者，实现成为核心网网元中的一部分。如图21所示，该装置2100可以包括：接收模块2110。
接收模块2110，用于接收来自终端设备的第一信息，所述第一信息包括所述终端设备针对核心网配置 的策略规则的使用情况相关的信息。
在一些实施例中，所述第一信息包括以下至少一种：
第一子信息，用于指示识别和/或未识别的策略规则；
第二子信息，用于指示建立PDU会话所使用的策略规则；
第三子信息，用于指示针对一个或多个应用所使用的策略规则；
第四子信息，用于指示针对一个或多个应用所使用的PDU会话和/或网络切片；
第五子信息，用于指示所述终端设备是否已使用更新的策略规则和/或所述终端设备使用的策略规则。
在一些实施例中，所述第二子信息还用于指示所述PDU会话与建立所述PDU会话所使用的策略规则之间的映射关系。
在一些实施例中，所述第三子信息还用于指示针对所述应用在不同时刻或不同时段所使用的策略规则。
在一些实施例中，所述网络切片以S-NSSAI标识。
在一些实施例中，所述接收模块2110，用于在核心网网元向所述终端设备发送下行消息之后，接收来自所述终端设备的所述下行消息对应的回复消息，所述回复消息中包括所述第一信息。
在一些实施例中，所述下行消息中包含的策略规则用于被所述终端设备评估，确定识别和/或未识别的策略规则后，生成所述第一信息。
在一些实施例中，所述回复消息包含在第一容器中。
在一些实施例中，所述下行消息为UCU消息。
在一些实施例中，所述第一信息复用所述回复消息中的已有字段，或者，所述第一信息使用所述回复消息中的新增字段。
在一些实施例中，使用新定义格式的所述回复消息传输所述第一信息。
在一些实施例中，所述接收模块2110，用于接收来自所述终端设备的上行消息，所述上行消息中包括所述第一信息。
在一些实施例中，所述接收模块2110，用于接收来自所述终端设备的注册请求消息，所述注册请求消息中包含第二容器，所述第二容器中包含所述上行消息。
在一些实施例中，所述注册请求消息包括以下至少一种：初始注册请求消息、周期性注册请求消息、位置更新的注册请求消息。
在一些实施例中，所述接收模块2110，还用于当所述第一信息发生变化时，接收所述终端设备发送的包含变化后的第一信息的注册请求消息，或者因其他原因触发所述终端设备发送的注册请求消息中携带所述变化后的第一信息。
在一些实施例中，所述上行消息为UE状态指示消息。
在一些实施例中，使用所述上行消息中的新增字段承载所述第一信息。
在一些实施例中，所述接收模块2110，用于接收所述终端设备发送PDU会话建立/修改请求，所述PDU会话建立/修改请求中包括所述第一信息。
在一些实施例中，所述接收模块2110，用于接收所述终端设备发送第一指示，所述第一指示用于指示所述终端设备支持上报所述第一信息和/或所述第一信息中的至少一个子信息；
和/或，所述装置2100还包括发送模块(图21中未示出)，用于向所述终端设备发送第二指示，所述第二指示用于指示所述核心网网元支持所述终端设备上报所述第一信息和/或所述第一信息中的至少一个子信息。
在一些实施例中，在基于UCU过程上报所述第一信息的情况下，所述核心网网元向所述终端设备发送的UCU消息中包括所述第二指示，和/或，所述UCU消息对应的回复消息中包括所述第一指示。
在一些实施例中，在基于终端注册过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的注册请求消息中包括所述第一指示，和/或，所述注册请求消息对应的回复消息中包括所述第二指示。
在一些实施例中，在基于PDU会话建立/修改过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的PDU会话建立/修改请求中包括所述第一指示，和/或，所述PDU会话建立/修改请求对应的回复消息中包括所述第二指示。
在一些实施例中，所述策略规则的指代方式包括以下至少一种：
采用所述策略规则的Rule ID进行指代；
采用所述策略规则的一个或多个参数进行指代。
在一些实施例中，在所述策略规则是UE URSP的情况下，采用所述策略规则的一个或多个参数进行指代，包括：采用所述URSP规则的Traffic descriptor和/或Rule Precedence，指代所述URSP规则；和/或，采用所述URSP规则下的RSD的Precedence和/或Route selection components，指代所述URSP规则下的RSD。
在一些实施例中，所述策略规则包括以下至少一种：URSP、V2XP、ProSeP、ANDSP。
在一些实施例中，在所述策略规则为URSP的情况下，所述第一信息所指示的策略规则包括URSP规则和/或所述URSP规则下的至少一个RSD。
请参考图22，其示出了本申请一个实施例提供的终端设备的结构示意图。该终端设备2200可以包括：处理器2201、收发器2202以及存储器2203。
处理器2201包括一个或者一个以上处理核心，处理器2201通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
收发器2202可以包括接收器和发射器，比如，该接收器和发射器可以实现为同一个无线通信组件，该无线通信组件可以包括一块无线通信芯片以及射频天线。
存储器2203可以与处理器2201以及收发器2202相连。
存储器2203可用于存储处理器执行的计算机程序，处理器2201用于执行该计算机程序，以实现上述方法实施例中的终端设备执行的各个步骤。
此外，存储器2203可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器，可擦除可编程只读存储器，静态随时存取存储器，只读存储器，磁存储器，快闪存储器，可编程只读存储器。
在示例性实施例中，所述收发器2202用于向核心网网元发送第一信息，所述第一信息包括所述终端设备针对核心网配置的策略规则的使用情况相关的信息。
对于本实施例中未详细说明的细节，可参见上文实施例，此处不再一一赘述。
请参考图23，其示出了本申请一个实施例提供的网络设备的结构示意图。该网络设备2300可以包括：处理器2301、收发器2302以及存储器2303。
处理器2301包括一个或者一个以上处理核心，处理器2301通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
收发器2302可以包括接收器和发射器。比如，该收发器2302可以包括一个有线通信组件，该有线通信组件可以包括一块有线通信芯片以及有线接口(比如光纤接口)。在一些实施例中，该收发器2302还可以包括一个无线通信组件，该无线通信组件可以包括一块无线通信芯片以及射频天线。
存储器2303可以与处理器2301以及收发器2302相连。
存储器2303可用于存储处理器执行的计算机程序，处理器2301用于执行该计算机程序，以实现上述方法实施例中的核心网网元执行的各个步骤。
此外，存储器2303可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器，可擦除可编程只读存储器，静态随时存取存储器，只读存储器，磁存储器，快闪存储器，可编程只读存储器。
在示例性实施例中，当网络设备为核心网网元时，所述收发器2302用于接收终端设备发送的第一信息，所述第一信息包括所述终端设备针对核心网配置的策略规则的使用情况相关的信息。
对于本实施例中未详细说明的细节，可参见上文实施例，此处不再一一赘述。
本申请实施例还提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序，所述计算机程序用于被终端设备的处理器执行，以实现上述终端设备侧的无线通信方法。
本申请实施例还提供了一种计算机可读存储介质，所述存储介质中存储有计算机程序，所述计算机程序用于被网络设备(如核心网网元)的处理器执行，以实现上述网络设备(如核心网网元)侧的无线通信方法。
可选地，该计算机可读存储介质可以包括：ROM(Read-Only Memory，只读存储器)、RAM(Random-Access Memory，随机存储器)、SSD(Solid State Drives，固态硬盘)或光盘等。其中，随机存取记忆体可以包括ReRAM(Resistance Random Access Memory，电阻式随机存取记忆体)和DRAM(Dynamic Random Access Memory，动态随机存取存储器)。
本申请实施例还提供了一种芯片，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片在终端设备上运行时，用于实现上述终端设备侧的无线通信方法。
本申请实施例还提供了一种芯片，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片在网络设备(如核心网网元)上运行时，用于实现上述网络设备(如核心网网元)侧的无线通信方法。
本申请实施例还提供了一种计算机程序产品或计算机程序，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，终端设备的处理器从所述计算机可读存储介质 读取并执行所述计算机指令，以实现上述终端设备侧的无线通信方法。
本申请实施例还提供了一种计算机程序产品或计算机程序，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，网络设备(如核心网网元)的处理器从所述计算机可读存储介质读取并执行所述计算机指令，以实现上述网络设备(如核心网网元)侧的无线通信方法。
应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。
在本申请实施例的描述中，术语“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。
在本申请一些实施例中，“预定义的”可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不作限定。比如预定义的可以是指协议中定义的。
在本申请一些实施例中，所述“协议”可以指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不作限定。
在本文中提及的“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
另外，本文中描述的步骤编号，仅示例性示出了步骤间的一种可能的执行先后顺序，在一些其它实施例中，上述步骤也可以不按照编号顺序来执行，如两个不同编号的步骤同时执行，或者两个不同编号的步骤按照与图示相反的顺序执行，本申请实施例对此不作限定。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请实施例所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上所述仅为本申请的示例性实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (108)

  1. 一种无线通信方法，其特征在于，所述方法包括：
    终端设备向核心网网元发送第一信息，所述第一信息包括所述终端设备针对核心网配置的策略规则的使用情况相关的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述第一信息包括以下至少一种：
    第一子信息，用于指示识别和/或未识别的策略规则；
    第二子信息，用于指示建立分组数据单元PDU会话所使用的策略规则；
    第三子信息，用于指示针对一个或多个应用所使用的策略规则；
    第四子信息，用于指示针对一个或多个应用所使用的PDU会话和/或网络切片；
    第五子信息，用于指示所述终端设备是否已使用更新的策略规则和/或所述终端设备使用的策略规则。
  3. 根据权利要求2所述的方法，其特征在于，所述第二子信息还用于指示所述PDU会话与建立所述PDU会话所使用的策略规则之间的映射关系。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第三子信息还用于指示针对所述应用在不同时刻或不同时段所使用的策略规则。
  5. 根据权利要求2至4任一项所述的方法，其特征在于，所述网络切片以单个网络切片选择辅助信息S-NSSAI标识。
  6. 根据权利要求1至5任一项所述的方法，其特征在于，所述终端设备向核心网网元发送第一信息，包括：
    所述终端设备在接收到所述核心网网元发送的下行消息之后，向所述核心网网元发送所述下行消息对应的回复消息，所述回复消息中包括所述第一信息。
  7. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述终端设备在接收到所述下行消息之后，对所述下行消息中包含的策略规则进行评估，确定识别和/或未识别的策略规则；
    所述终端设备根据所述识别和/或未识别的策略规则，生成所述第一信息。
  8. 根据权利要求6或7所述的方法，其特征在于，所述回复消息包含在第一容器中。
  9. 根据权利要求6至8任一项所述的方法，其特征在于，所述下行消息为用户设备配置更新UCU消息。
  10. 根据权利要求6至9任一项所述的方法，其特征在于，所述第一信息复用所述回复消息中的已有字段，或者，所述第一信息使用所述回复消息中的新增字段。
  11. 根据权利要求6至9任一项所述的方法，其特征在于，使用新定义格式的所述回复消息传输所述第一信息。
  12. 根据权利要求1至5任一项所述的方法，其特征在于，所述终端设备向核心网网元发送第一信息，包括：
    所述终端设备向所述核心网网元发送上行消息，所述上行消息中包括所述第一信息。
  13. 根据权利要求12所述的方法，其特征在于，所述终端设备向所述核心网网元发送上行消息包括：
    所述终端设备向所述核心网网元发送注册请求消息，所述注册请求消息中包含第二容器，所述第二容器中包含所述上行消息。
  14. 根据权利要求13所述的方法，其特征在于，所述注册请求消息包括以下至少一种：初始注册请求消息、周期性注册请求消息、位置更新的注册请求消息。
  15. 根据权利要求13或14所述的方法，其特征在于，所述方法还包括：
    当所述第一信息发生变化时，所述终端设备向所述核心网网元发送包含变化后的第一信息的注册请求消息，或者因其他原因触发向所述核心网网元发送的注册请求消息中携带所述变化后的第一信息。
  16. 根据权利要求12至15任一项所述的方法，其特征在于，所述上行消息为UE状态指示消息。
  17. 根据权利要求12至16任一项所述的方法，其特征在于，使用所述上行消息中的新增字段承载所述第一信息。
  18. 根据权利要求1至5任一项所述的方法，其特征在于，所述终端设备向核心网网元发送第一信息，包括：
    所述终端设备向所述核心网网元发送PDU会话建立/修改请求，所述PDU会话建立/修改请求中包括所述第一信息。
  19. 根据权利要求1至18任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备向所述核心网网元发送第一指示，所述第一指示用于指示所述终端设备支持上报所述第 一信息和/或所述第一信息中的至少一个子信息；
    和/或，
    所述终端设备接收来自所述核心网网元的第二指示，所述第二指示用于指示所述核心网网元支持所述终端设备上报所述第一信息和/或所述第一信息中的至少一个子信息。
  20. 根据权利要求19所述的方法，其特征在于，在基于UCU过程上报所述第一信息的情况下，所述核心网网元向所述终端设备发送的UCU消息中包括所述第二指示，和/或，所述UCU消息对应的回复消息中包括所述第一指示。
  21. 根据权利要求19所述的方法，其特征在于，在基于终端注册过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的注册请求消息中包括所述第一指示，和/或，所述注册请求消息对应的回复消息中包括所述第二指示。
  22. 根据权利要求19所述的方法，其特征在于，在基于PDU会话建立/修改过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的PDU会话建立/修改请求中包括所述第一指示，和/或，所述PDU会话建立/修改请求对应的回复消息中包括所述第二指示。
  23. 根据权利要求1至22任一项所述的方法，其特征在于，所述策略规则的指代方式包括以下至少一种：
    采用所述策略规则的规则标识RuleID进行指代；
    采用所述策略规则的一个或多个参数进行指代。
  24. 根据权利要求23所述的方法，其特征在于，在所述策略规则是UE路由选择策略URSP的情况下，采用所述策略规则的一个或多个参数进行指代，包括：
    采用所述URSP规则的业务描述符Traffic descriptor和/或规则优先级Rule Precedence，指代所述URSP规则；
    和/或，
    采用所述URSP规则下的路由选择描述符RSD的优先级Precedence和/或路由选择组分Route selection components，指代所述URSP规则下的RSD。
  25. 根据权利要求1至24任一项所述的方法，其特征在于，所述策略规则包括以下至少一种：URSP、车联网策略V2XP、邻近服务策略ProSeP、接入网发现和选择策略ANDSP。
  26. 根据权利要求1至25任一项所述的方法，其特征在于，在所述策略规则为URSP的情况下，所述第一信息所指示的策略规则包括URSP规则和/或所述URSP规则下的至少一个RSD。
  27. 一种无线通信方法，其特征在于，所述方法包括：
    核心网网元接收来自终端设备的第一信息，所述第一信息包括所述终端设备针对核心网配置的策略规则的使用情况相关的信息。
  28. 根据权利要求27所述的方法，其特征在于，所述第一信息包括以下至少一种：
    第一子信息，用于指示识别和/或未识别的策略规则；
    第二子信息，用于指示建立分组数据单元PDU会话所使用的策略规则；
    第三子信息，用于指示针对一个或多个应用所使用的策略规则；
    第四子信息，用于指示针对一个或多个应用所使用的PDU会话和/或网络切片；
    第五子信息，用于指示所述终端设备是否已使用更新的策略规则和/或所述终端设备使用的策略规则。
  29. 根据权利要求28所述的方法，其特征在于，所述第二子信息还用于指示所述PDU会话与建立所述PDU会话所使用的策略规则之间的映射关系。
  30. 根据权利要求28或29所述的方法，其特征在于，所述第三子信息还用于指示针对所述应用在不同时刻或不同时段所使用的策略规则。
  31. 根据权利要求28至30任一项所述的方法，其特征在于，所述网络切片以单个网络切片选择辅助信息S-NSSAI标识。
  32. 根据权利要求23至27任一项所述的方法，其特征在于，所述核心网网元接收来自终端设备的第一信息，包括：
    在所述核心网网元向所述终端设备发送下行消息之后，所述核心网网元接收来自所述终端设备的所述下行消息对应的回复消息，所述回复消息中包括所述第一信息。
  33. 根据权利要求32所述的方法，其特征在于，所述下行消息中包含的策略规则用于被所述终端设备评估，确定识别和/或未识别的策略规则后，生成所述第一信息。
  34. 根据权利要求32或33所述的方法，其特征在于，所述回复消息包含在第一容器中。
  35. 根据权利要求32至34任一项所述的方法，其特征在于，所述下行消息为用户设备配置更新UCU 消息。
  36. 根据权利要求32至35任一项所述的方法，其特征在于，所述第一信息复用所述回复消息中的已有字段，或者，所述第一信息使用所述回复消息中的新增字段。
  37. 根据权利要求32至35任一项所述的方法，其特征在于，使用新定义格式的所述回复消息传输所述第一信息。
  38. 根据权利要求27至31任一项所述的方法，其特征在于，所述核心网网元接收来自终端设备的第一信息，包括：
    所述核心网网元接收来自所述终端设备的上行消息，所述上行消息中包括所述第一信息。
  39. 根据权利要求38所述的方法，其特征在于，所述核心网网元接收来自所述终端设备的上行消息，包括：
    所述核心网网元接收来自所述终端设备的注册请求消息，所述注册请求消息中包含第二容器，所述第二容器中包含所述上行消息。
  40. 根据权利要求39所述的方法，其特征在于，所述注册请求消息包括以下至少一种：初始注册请求消息、周期性注册请求消息、位置更新的注册请求消息。
  41. 根据权利要求39或40所述的方法，其特征在于，所述方法还包括：
    当所述第一信息发生变化时，所述核心网网元接收所述终端设备发送的包含变化后的第一信息的注册请求消息，或者因其他原因触发所述终端设备发送的注册请求消息中携带所述变化后的第一信息。
  42. 根据权利要求38至41任一项所述的方法，其特征在于，所述上行消息为UE状态指示消息。
  43. 根据权利要求38至42任一项所述的方法，其特征在于，使用所述上行消息中的新增字段承载所述第一信息。
  44. 根据权利要求27至31任一项所述的方法，其特征在于，所述核心网网元接收来自所述终端设备的第一信息，包括：
    所述核心网网元接收所述终端设备发送PDU会话建立/修改请求，所述PDU会话建立/修改请求中包括所述第一信息。
  45. 根据权利要求27至44任一项所述的方法，其特征在于，所述方法还包括：
    所述核心网网元接收所述终端设备发送的第一指示，所述第一指示用于指示所述终端设备支持上报所述第一信息和/或所述第一信息中的至少一个子信息；
    和/或，
    所述核心网网元向所述终端设备发送第二指示，所述第二指示用于指示所述核心网网元支持所述终端设备上报所述第一信息和/或所述第一信息中的至少一个子信息。
  46. 根据权利要求45所述的方法，其特征在于，在基于UCU过程上报所述第一信息的情况下，所述核心网网元向所述终端设备发送的UCU消息中包括所述第二指示，和/或，所述UCU消息对应的回复消息中包括所述第一指示。
  47. 根据权利要求45所述的方法，其特征在于，在基于终端注册过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的注册请求消息中包括所述第一指示，和/或，所述注册请求消息对应的回复消息中包括所述第二指示。
  48. 根据权利要求45所述的方法，其特征在于，在基于PDU会话建立/修改过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的PDU会话建立/修改请求中包括所述第一指示，和/或，所述PDU会话建立/修改请求对应的回复消息中包括所述第二指示。
  49. 根据权利要求27至48任一项所述的方法，其特征在于，所述策略规则的指代方式包括以下至少一种：
    采用所述策略规则的规则标识Rule ID进行指代；
    采用所述策略规则的一个或多个参数进行指代。
  50. 根据权利要求49所述的方法，其特征在于，在所述策略规则是UE路由选择策略URSP的情况下，采用所述策略规则的一个或多个参数进行指代，包括：
    采用所述URSP规则的业务描述符Traffic descriptor和/或规则优先级Rule Precedence，指代所述URSP规则；
    和/或，
    采用所述URSP规则下的路由选择描述符RSD的优先级Precedence和/或路由选择组分Route selection components，指代所述URSP规则下的RSD。
  51. 根据权利要求27至50任一项所述的方法，其特征在于，所述策略规则包括以下至少一种：UEURSP、车联网策略V2XP、邻近服务策略ProSeP、接入网发现和选择策略ANDSP。
  52. 根据权利要求27至51任一项所述的方法，其特征在于，在所述策略规则为URSP的情况下，所述第一信息所指示的策略规则包括URSP规则和/或所述URSP规则下的至少一个RSD。
  53. 一种无线通信装置，其特征在于，所述装置包括：
    发送模块，用于向核心网网元发送第一信息，所述第一信息包括终端设备针对核心网配置的策略规则的使用情况相关的信息。
  54. 根据权利要求53所述的装置，其特征在于，所述第一信息包括以下至少一种：
    第一子信息，用于指示识别和/或未识别的策略规则；
    第二子信息，用于指示建立分组数据单元PDU会话所使用的策略规则；
    第三子信息，用于指示针对一个或多个应用所使用的策略规则；
    第四子信息，用于指示针对一个或多个应用所使用的PDU会话和/或网络切片；
    第五子信息，用于指示所述终端设备是否已使用更新的策略规则和/或所述终端设备使用的策略规则。
  55. 根据权利要求54所述的装置，其特征在于，所述第二子信息还用于指示所述PDU会话与建立所述PDU会话所使用的策略规则之间的映射关系。
  56. 根据权利要求54或55所述的装置，其特征在于，所述第三子信息还用于指示针对所述应用在不同时刻或不同时段所使用的策略规则。
  57. 根据权利要求54至56任一项所述的装置，其特征在于，所述网络切片以单个网络切片选择辅助信息S-NSSAI标识。
  58. 根据权利要求53至57任一项所述的装置，其特征在于，
    所述发送模块，用于在接收到所述核心网网元发送的下行消息之后，向所述核心网网元发送所述下行消息对应的回复消息，所述回复消息中包括所述第一信息。
  59. 根据权利要求58所述的装置，其特征在于，所述装置还包括处理模块，用于：
    在接收到所述下行消息之后，对所述下行消息中包含的策略规则进行评估，确定识别和/或未识别的策略规则；
    根据所述识别和/或未识别的策略规则，生成所述第一信息。
  60. 根据权利要求58或59所述的装置，其特征在于，所述回复消息包含在第一容器中。
  61. 根据权利要求58至60任一项所述的装置，其特征在于，所述下行消息为用户设备配置更新UCU消息。
  62. 根据权利要求60至61任一项所述的装置，其特征在于，所述第一信息复用所述回复消息中的已有字段，或者，所述第一信息使用所述回复消息中的新增字段。
  63. 根据权利要求60至61任一项所述的装置，其特征在于，使用新定义格式的所述回复消息传输所述第一信息。
  64. 根据权利要求53至57任一项所述的装置，其特征在于，
    所述发送模块，用于向所述核心网网元发送上行消息，所述上行消息中包括所述第一信息。
  65. 根据权利要求64所述的装置，其特征在于，
    所述发送模块，用于向所述核心网网元发送注册请求消息，所述注册请求消息中包含第二容器，所述第二容器中包含所述上行消息。
  66. 根据权利要求65所述的装置，其特征在于，所述注册请求消息包括以下至少一种：初始注册请求消息、周期性注册请求消息、位置更新的注册请求消息。
  67. 根据权利要求65或66所述的装置，其特征在于，
    所述发送模块，还用于当所述第一信息发生变化时，向所述核心网网元发送包含变化后的第一信息的注册请求消息，或者因其他原因触发向所述核心网网元发送的注册请求消息中携带所述变化后的第一信息。
  68. 根据权利要求64至67任一项所述的装置，其特征在于，所述上行消息为UE状态指示消息。
  69. 根据权利要求64至67任一项所述的装置，其特征在于，使用所述上行消息中的新增字段承载所述第一信息。
  70. 根据权利要求53至57任一项所述的装置，其特征在于，
    所述发送模块，用于向所述核心网网元发送PDU会话建立/修改请求，所述PDU会话建立/修改请求中包括所述第一信息。
  71. 根据权利要求53至70任一项所述的装置，其特征在于，
    所述发送模块，还用于向所述核心网网元发送第一指示，所述第一指示用于指示所述终端设备支持上报所述第一信息和/或所述第一信息中的至少一个子信息；
    和/或，
    所述装置还包括接收模块，用于接收来自所述核心网网元的第二指示，所述第二指示用于指示所述核心网网元支持所述终端设备上报所述第一信息和/或所述第一信息中的至少一个子信息。
  72. 根据权利要求71所述的装置，其特征在于，在基于UCU过程上报所述第一信息的情况下，所述核心网网元向所述终端设备发送的UCU消息中包括所述第二指示，和/或，所述UCU消息对应的回复消息中包括所述第一指示。
  73. 根据权利要求71所述的装置，其特征在于，在基于终端注册过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的注册请求消息中包括所述第一指示，和/或，所述注册请求消息对应的回复消息中包括所述第二指示。
  74. 根据权利要求71所述的装置，其特征在于，在基于PDU会话建立/修改过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的PDU会话建立/修改请求中包括所述第一指示，和/或，所述PDU会话建立/修改请求对应的回复消息中包括所述第二指示。
  75. 根据权利要求53至74任一项所述的装置，其特征在于，所述策略规则的指代方式包括以下至少一种：
    采用所述策略规则的规则标识RuleID进行指代；
    采用所述策略规则的一个或多个参数进行指代。
  76. 根据权利要求75所述的装置，其特征在于，在所述策略规则是UE路由选择策略URSP的情况下，采用所述策略规则的一个或多个参数进行指代，包括：
    采用所述URSP规则的业务描述符Traffic descriptor和/或规则优先级Rule Precedence，指代所述URSP规则；
    和/或，
    采用所述URSP规则下的路由选择描述符RSD的优先级Precedence和/或路由选择组分Route selection components，指代所述URSP规则下的RSD。
  77. 根据权利要求53至76任一项所述的装置，其特征在于，所述策略规则包括以下至少一种：UEURSP、车联网策略V2XP、邻近服务策略ProSeP、接入网发现和选择策略ANDSP。
  78. 根据权利要求53至77任一项所述的装置，其特征在于，在所述策略规则为URSP的情况下，所述第一信息所指示的策略规则包括URSP规则和/或所述URSP规则下的至少一个RSD。
  79. 一种无线通信装置，其特征在于，所述装置包括：
    接收模块，用于接收来自终端设备的第一信息，所述第一信息包括所述终端设备针对核心网配置的策略规则的使用情况相关的信息。
  80. 根据权利要求79所述的装置，其特征在于，所述第一信息包括以下至少一种：
    第一子信息，用于指示识别和/或未识别的策略规则；
    第二子信息，用于指示建立分组数据单元PDU会话所使用的策略规则；
    第三子信息，用于指示针对一个或多个应用所使用的策略规则；
    第四子信息，用于指示针对一个或多个应用所使用的PDU会话和/或网络切片；
    第五子信息，用于指示所述终端设备是否已使用更新的策略规则和/或所述终端设备使用的策略规则。
  81. 根据权利要求80所述的装置，其特征在于，所述第二子信息还用于指示所述PDU会话与建立所述PDU会话所使用的策略规则之间的映射关系。
  82. 根据权利要求80或81所述的装置，其特征在于，所述第三子信息还用于指示针对所述应用在不同时刻或不同时段所使用的策略规则。
  83. 根据权利要求80至82任一项所述的装置，其特征在于，所述网络切片以单个网络切片选择辅助信息S-NSSAI标识。
  84. 根据权利要求79至83任一项所述的装置，其特征在于，
    所述接收模块，用于在核心网网元向所述终端设备发送下行消息之后，接收来自所述终端设备的所述下行消息对应的回复消息，所述回复消息中包括所述第一信息。
  85. 根据权利要求84所述的装置，其特征在于，所述下行消息中包含的策略规则用于被所述终端设备评估，确定识别和/或未识别的策略规则后，生成所述第一信息。
  86. 根据权利要求84或85所述的装置，其特征在于，所述回复消息包含在第一容器中。
  87. 根据权利要求84至86任一项所述的装置，其特征在于，所述下行消息为用户设备配置更新UCU消息。
  88. 根据权利要求84至87任一项所述的装置，其特征在于，所述第一信息复用所述回复消息中的已有字段，或者，所述第一信息使用所述回复消息中的新增字段。
  89. 根据权利要求884至87任一项所述的装置，其特征在于，使用新定义格式的所述回复消息传输所述第一信息。
  90. 根据权利要求79至83任一项所述的装置，其特征在于，
    所述接收模块，用于接收来自所述终端设备的上行消息，所述上行消息中包括所述第一信息。
  91. 根据权利要求90所述的装置，其特征在于，
    所述接收模块，用于接收来自所述终端设备的注册请求消息，所述注册请求消息中包含第二容器，所述第二容器中包含所述上行消息。
  92. 根据权利要求91所述的装置，其特征在于，所述注册请求消息包括以下至少一种：初始注册请求消息、周期性注册请求消息、位置更新的注册请求消息。
  93. 根据权利要求91或92所述的装置，其特征在于，
    所述接收模块，还用于当所述第一信息发生变化时，接收所述终端设备发送的包含变化后的第一信息的注册请求消息，或者因其他原因触发所述终端设备发送的注册请求消息中携带所述变化后的第一信息。
  94. 根据权利要求90至93任一项所述的装置，其特征在于，所述上行消息为UE状态指示消息。
  95. 根据权利要求90至94任一项所述的装置，其特征在于，使用所述上行消息中的新增字段承载所述第一信息。
  96. 根据权利要求79至83任一项所述的装置，其特征在于，
    所述接收模块，用于接收所述终端设备发送PDU会话建立/修改请求，所述PDU会话建立/修改请求中包括所述第一信息。
  97. 根据权利要求79至96任一项所述的装置，其特征在于，
    所述接收模块，还用于接收所述终端设备发送第一指示，所述第一指示用于指示所述终端设备支持上报所述第一信息和/或所述第一信息中的至少一个子信息；
    和/或，
    所述装置还包括发送模块，用于向终端设备发送第二指示，所述第二指示用于指示所述核心网网元支持所述终端设备上报所述第一信息和/或所述第一信息中的至少一个子信息。
  98. 根据权利要求97所述的装置，其特征在于，在基于UCU过程上报所述第一信息的情况下，所述核心网网元向所述终端设备发送的UCU消息中包括所述第二指示，和/或，所述UCU消息对应的回复消息中包括所述第一指示。
  99. 根据权利要求97所述的装置，其特征在于，在基于终端注册过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的注册请求消息中包括所述第一指示，和/或，所述注册请求消息对应的回复消息中包括所述第二指示。
  100. 根据权利要求97所述的装置，其特征在于，在基于PDU会话建立/修改过程上报所述第一信息的情况下，所述终端设备向所述核心网网元发送的PDU会话建立/修改请求中包括所述第一指示，和/或，所述PDU会话建立/修改请求对应的回复消息中包括所述第二指示。
  101. 根据权利要求79至100任一项所述的装置，其特征在于，所述策略规则的指代方式包括以下至少一种：
    采用所述策略规则的规则标识Rule ID进行指代；
    采用所述策略规则的一个或多个参数进行指代。
  102. 根据权利要求101所述的装置，其特征在于，在所述策略规则是UE路由选择策略URSP的情况下，采用所述策略规则的一个或多个参数进行指代，包括：
    采用所述URSP规则的业务描述符Traffic descriptor和/或规则优先级Rule Precedence，指代所述URSP规则；
    和/或，
    采用所述URSP规则下的路由选择描述符RSD的优先级Precedence和/或路由选择组分Route selection components，指代所述URSP规则下的RSD。
  103. 根据权利要求79至102任一项所述的装置，其特征在于，所述策略规则包括以下至少一种：UEURSP、车联网策略V2XP、邻近服务策略ProSeP、接入网发现和选择策略ANDSP。
  104. 根据权利要求79至103任一项所述的装置，其特征在于，在所述策略规则为URSP的情况下，所述第一信息所指示的策略规则包括URSP规则和/或所述URSP规则下的至少一个RSD。
  105. 一种通信设备，其特征在于，所述通信设备包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述计算机程序以实现如权利要求1至26任一项所述的方法，或者实现如权利要求27至52任一项所述的方法。
  106. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有计算机程序，所述计算机程序由处理器加载并执行以实现如权利要求1至26任一项所述的方法，或者实现如权利要求27至52任一项所述的方法。
  107. 一种芯片，其特征在于，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片运行时，用于实现如权利要求1至26任一项所述的方法，或者实现如权利要求27至52任一项所述的方法。
  108. 一种计算机程序产品或计算机程序，其特征在于，所述计算机程序产品或计算机程序包括计算机指令，所述计算机指令存储在计算机可读存储介质中，处理器从所述计算机可读存储介质读取并执行所述计算机指令，以实现如权利要求1至26任一项所述的方法，或者实现如权利要求27至52任一项所述的方法。
PCT/CN2022/078902 2022-03-02 2022-03-02 无线通信方法、装置、设备、存储介质及程序产品 WO2023164849A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/078902 WO2023164849A1 (zh) 2022-03-02 2022-03-02 无线通信方法、装置、设备、存储介质及程序产品

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/078902 WO2023164849A1 (zh) 2022-03-02 2022-03-02 无线通信方法、装置、设备、存储介质及程序产品

Publications (2)

Publication Number Publication Date
WO2023164849A1 true WO2023164849A1 (zh) 2023-09-07
WO2023164849A9 WO2023164849A9 (zh) 2023-10-05

Family

ID=87882803

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/078902 WO2023164849A1 (zh) 2022-03-02 2022-03-02 无线通信方法、装置、设备、存储介质及程序产品

Country Status (1)

Country Link
WO (1) WO2023164849A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110519825A (zh) * 2018-05-21 2019-11-29 中国移动通信有限公司研究院 路由选择策略的处理方法、装置、相关设备和存储介质
WO2021046803A1 (en) * 2019-09-12 2021-03-18 Telefonaktiebolaget Lm Ericsson (Publ) Method, device, computer-readable storage and carrier for policy control
WO2021217412A1 (zh) * 2020-04-28 2021-11-04 Oppo广东移动通信有限公司 一种确定终端策略行为的方法及装置、网络设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110519825A (zh) * 2018-05-21 2019-11-29 中国移动通信有限公司研究院 路由选择策略的处理方法、装置、相关设备和存储介质
WO2021046803A1 (en) * 2019-09-12 2021-03-18 Telefonaktiebolaget Lm Ericsson (Publ) Method, device, computer-readable storage and carrier for policy control
WO2021217412A1 (zh) * 2020-04-28 2021-11-04 Oppo广东移动通信有限公司 一种确定终端策略行为的方法及装置、网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SAMSUNG: "Triggering of UE Policy Association", 3GPP TSG-SA WG2 MEETING #136, S2-1911664, 8 November 2019 (2019-11-08), XP051821742 *

Also Published As

Publication number Publication date
WO2023164849A9 (zh) 2023-10-05

Similar Documents

Publication Publication Date Title
CN110063084B (zh) 在无线通信系统中选择会话和服务连续性模式的方法
US20210168151A1 (en) Method for implementing user plane security policy, apparatus, and system
US20220264258A1 (en) Communications Method and Apparatus, and Device
EP3972335A1 (en) Method, device and system for managing background data transfer policies
CN113543165B (zh) 通信方法、装置及系统
US20190208562A1 (en) Method and user equipment for connecting by means of plurality of accesses in next generation network
WO2021022460A1 (zh) 一种会话验证方法、电子设备及存储介质
US11265771B2 (en) AT commands for supporting session and service continuity modes of 5G protocol data unitsession operations
US20230132454A1 (en) Method and apparatus for supporting edge computing service for roaming ue in wireless communication system
US20230018378A1 (en) Parameter configuration method, apparatus and system, device and storage medium
US20230388909A1 (en) Ensuring network control of simultaneous access to network slices with application awareness
WO2023164849A1 (zh) 无线通信方法、装置、设备、存储介质及程序产品
US20230071815A1 (en) Path section between uu and pc5
WO2021208059A1 (zh) 连接建立方法、装置、设备及存储介质
CN115190457A (zh) 语音通信的方法和装置
US20220124158A1 (en) Method and apparatus for changing data transmission scheme, device, and storage medium
EP4216622A2 (en) Network registration method for traffic steering and device supporting the same
WO2022222748A1 (zh) 中继通信方法和装置
US20230371094A1 (en) Communication method and apparatus
WO2023137579A1 (zh) 紧急业务的提供方法、装置、设备及存储介质
WO2023184193A1 (zh) 无线通信方法、装置、设备、存储介质及程序产品
WO2024032041A1 (zh) 通信方法和通信装置
WO2024027260A1 (zh) 通信方法、终端、通信装置及存储介质
WO2023015973A1 (zh) 一种网络切片准入控制方法和装置
WO2023103575A1 (zh) 组播/广播通信的方法与相关装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22929300

Country of ref document: EP

Kind code of ref document: A1