WO2020186529A1 - 一种策略确定方法及装置、终端 - Google Patents

一种策略确定方法及装置、终端 Download PDF

Info

Publication number
WO2020186529A1
WO2020186529A1 PCT/CN2019/079141 CN2019079141W WO2020186529A1 WO 2020186529 A1 WO2020186529 A1 WO 2020186529A1 CN 2019079141 W CN2019079141 W CN 2019079141W WO 2020186529 A1 WO2020186529 A1 WO 2020186529A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
type
strategy
information
terminal
Prior art date
Application number
PCT/CN2019/079141
Other languages
English (en)
French (fr)
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
Priority to SG11202104142UA priority Critical patent/SG11202104142UA/en
Priority to KR1020217011680A priority patent/KR20210145121A/ko
Priority to CN202010584970.6A priority patent/CN111741479B/zh
Priority to BR112021009804-6A priority patent/BR112021009804A2/pt
Priority to CA3117244A priority patent/CA3117244C/en
Priority to PCT/CN2019/079141 priority patent/WO2020186529A1/zh
Priority to AU2019435787A priority patent/AU2019435787A1/en
Priority to MX2021006369A priority patent/MX2021006369A/es
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to JP2021521537A priority patent/JP7301962B2/ja
Priority to EP19919915.9A priority patent/EP3846579B1/en
Priority to CN201980005882.1A priority patent/CN111989984A/zh
Publication of WO2020186529A1 publication Critical patent/WO2020186529A1/zh
Priority to US17/037,551 priority patent/US11153444B2/en
Priority to US17/364,421 priority patent/US11516350B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/14Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403Architecture for metering, charging or billing
    • H04L12/1407Policy-and-charging control [PCC] architecture
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/61Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on the service used
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/62Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP based on trigger specification
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M15/00Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66Policy and charging system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24Accounting or billing
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30Services specially adapted for particular environments, situations or purposes
    • H04W4/40Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/02Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08Mobility data transfer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/18Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04Large scale networks; Deep hierarchical networks
    • H04W84/042Public Land Mobile systems, e.g. cellular systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W92/00Interfaces specially adapted for wireless communication networks
    • H04W92/16Interfaces between hierarchically similar devices
    • H04W92/18Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the embodiments of the present application relate to the field of mobile communication technology, and in particular to a method and device for determining a strategy, and a terminal.
  • UE policy User Equipment policy
  • PSI Policy Section Identifier
  • the embodiments of the present application provide a method and device for determining a strategy, a terminal, and a network device.
  • the terminal receives first information sent by the network device, where the first information includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and an indication of whether the terminal is allowed to request the first policy Information, the terminal requests the trigger condition of the first strategy.
  • the terminal sends a first request message to the network device, where the first request message includes second information, and the second information is used to instruct the network device to update the target policy type and/or the policy corresponding to the target service type.
  • the receiving unit is configured to receive first information sent by a network device, where the first information includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether the terminal is allowed to request the first
  • the indication information of a strategy and the trigger condition of the terminal requesting the first strategy is configured to receive first information sent by a network device, where the first information includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether the terminal is allowed to request the first
  • the indication information of a strategy and the trigger condition of the terminal requesting the first strategy includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether the terminal is allowed to request the first
  • the indication information of a strategy and the trigger condition of the terminal requesting the first strategy is configured to receive first information sent by a network device, where the first information includes at
  • the sending unit is configured to send a first request message to the network device, where the first request message includes second information, and the second information is used to instruct the network device to update the target policy type and/or target service type correspondence Strategy.
  • the terminal provided in the embodiment of the present application includes a processor and a memory.
  • the memory is used to store a computer program
  • the processor is used to call and run the computer program stored in the memory to execute the above-mentioned strategy determination method.
  • the chip provided in the embodiment of the present application is used to implement the aforementioned strategy determination method.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned policy determination method.
  • the computer-readable storage medium provided by the embodiment of the present application is used to store a computer program, and the computer program enables a computer to execute the above-mentioned policy determination method.
  • the computer program product provided by the embodiment of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned policy determination method.
  • the computer program provided in the embodiment of the present application when it runs on a computer, causes the computer to execute the above-mentioned policy determination method.
  • the terminal receives the first information sent by the network device, the first information includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether the terminal request is allowed
  • the indication information of the first policy and the trigger condition of the terminal requesting the first policy in this way, the terminal can be made aware of which policy type the policy belongs to, so that the network side can be specifically requested to update the policy of a specific policy type.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • Figure 2 is a flow chart of the configuration of the UE policy provided by an embodiment of the present application.
  • FIG. 3 is a flowchart of a UE actively requesting a UE policy according to an embodiment of this application;
  • FIG. 4 is a first flowchart of a method for determining a strategy provided by an embodiment of the present application
  • Figure 5-1 is a schematic diagram of the information unit of the UE policy section management list
  • Figure 5-2 is a schematic diagram of the content of the UE policy section management list
  • Figure 5-3 is a schematic diagram of UE policy section management sublist
  • Figure 5-4 is a schematic diagram of UE policy section management sublist content
  • Figure 5-5 is a schematic diagram of Instruction
  • Figure 5-6 is a schematic diagram of the content of the UE policy section
  • Figure 5-7 is a schematic diagram of the UE policy part
  • Figure 6-1 is a schematic diagram 1 of the PSI structure provided by an embodiment of the present application.
  • Figure 6-2 is a second schematic diagram of the PSI structure provided by an embodiment of the present application.
  • FIG. 7 is a diagram of the correspondence between PSI and service types provided by an embodiment of the present application.
  • FIG. 8 is a second schematic flowchart of a method for determining a strategy provided by an embodiment of the present application.
  • Figure 9-1 is a schematic diagram of the information unit of the UPSI list
  • FIG. 9-2 is a schematic diagram of the UPSI sublist
  • FIG. 10 is a schematic diagram 1 of the structural composition of a policy determining apparatus provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram 2 of the structural composition of the policy determination apparatus provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a chip of an embodiment of the present application.
  • FIG. 14 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GSM Global System of Mobile Communication
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the communication system 100 applied in the embodiment of the present application is shown in FIG. 1.
  • the communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal 120 (or called a communication terminal or a terminal).
  • the network device 110 may provide communication coverage for a specific geographic area, and may communicate with terminals located in the coverage area.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, a base station (NodeB, NB) in a WCDMA system, or an evolved base station in an LTE system (Evolutional Node B, eNB or eNodeB), or the wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches, bridges, routers, network-side devices in 5G networks, or network devices in the future evolution of the Public Land Mobile Network (PLMN), etc.
  • BTS Base Transceiver Station
  • NodeB, NB base station
  • LTE Long Term Evolutional Node B
  • eNB evolved base station
  • CRAN Cloud Radio Access Network
  • the network equipment can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, Wearable devices, hubs, switches
  • the communication system 100 also includes at least one terminal 120 located within the coverage area of the network device 110.
  • the "terminal” used here includes, but is not limited to, connection via wired lines, such as public switched telephone networks (PSTN), digital subscriber lines (Digital Subscriber Line, DSL), digital cables, and direct cable connections; And/or another data connection/network; and/or via a wireless interface, such as for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks, satellite networks, AM-FM Broadcast transmitter; and/or another terminal's device configured to receive/send communication signals; and/or Internet of Things (IoT) equipment.
  • a terminal set to communicate through a wireless interface may be referred to as a "wireless communication terminal", a “wireless terminal” or a “mobile terminal”.
  • mobile terminals include, but are not limited to, satellites or cellular phones; Personal Communications System (PCS) terminals that can combine cellular radio phones with data processing, fax, and data communication capabilities; can include radio phones, pagers, Internet/intranet PDA with internet access, web browser, memo pad, calendar, and/or Global Positioning System (GPS) receiver; and conventional laptop and/or palmtop receivers or others including radio phone transceivers Electronic device.
  • PCS Personal Communications System
  • GPS Global Positioning System
  • Terminal can refer to access terminal, user equipment (User Equipment, UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user Device.
  • Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital processing (Personal Digital Assistant, PDA), with wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in 5G networks, or terminals in the future evolution of PLMN, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminals 120 may perform device-to-device (D2D) communication.
  • D2D device-to-device
  • the 5G system or 5G network may also be referred to as a New Radio (NR) system or NR network.
  • NR New Radio
  • FIG. 1 exemplarily shows one network device and two terminals.
  • the communication system 100 may include multiple network devices and the coverage of each network device may include other numbers of terminals. This embodiment of the present application There is no restriction on this.
  • the communication system 100 may also include other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • the devices with communication functions in the network/system in the embodiments of the present application may be referred to as communication devices.
  • the communication device may include a network device 110 and a terminal 120 with communication functions, and the network device 110 and the terminal 120 may be the specific devices described above, which will not be repeated here;
  • the device may also include other devices in the communication system 100, such as other network entities such as a network controller and a mobility management entity, which are not limited in the embodiment of the present application.
  • WLAN Selection Policy WLAN Selection Policy, WLANSP
  • WLANSP contains multiple rules.
  • the rules in WLANSP are called WLANSP rules, which are used when the UE selects which WLAN access point.
  • the URSP contains multiple rules.
  • the rules in the URSP are called URSP Rules, and each URSP Rule consists of a traffic description (Traffic Descriptor) and a set of routing descriptions (Route Selection Descriptor, RSD).
  • URSP Rules consists of a traffic description (Traffic Descriptor) and a set of routing descriptions (Route Selection Descriptor, RSD).
  • Traffic Descriptor Traffic Descriptor
  • RSD Roue Selection Descriptor
  • UE policies In addition to the types of UE policies that include URSP and WLANSP, they can also be differentiated in terms of usage. For example, some UE policies are used for eMBB services, and some UE policies are used for V2X services. Further, V2X strategies are divided into PC5 strategies and Uu interface strategies.
  • the configuration of the UE policy is implemented through the UE Configuration Update (UCU) process, as shown in Figure 2, the process includes the following steps:
  • Step 201 A policy control function network element (Policy Control Function, PCF) decides to update the UE policy.
  • Policy Control Function Policy Control Function
  • Step 202 The PCF puts the UE policy to be updated in a container and sends it to the core access and mobility management network element (Core Access and Mobility Management Function, AMF).
  • AMF Core Access and Mobility Management Function
  • Step 203 The AMF uses the NAS message to directly forward the container to the UE.
  • 3GPP stipulates a process for the UE to actively request a UE policy. As shown in Figure 3, the process includes the following steps:
  • Step 301 The UE sends a UE policy request message to the AMF.
  • Step 302 The AMF sends a UE policy control update message to the PCF.
  • Step 303 Perform a UE policy configuration process between the UE and the PCF.
  • the configuration flow of the UE policy refers to the flow shown in FIG. 2.
  • the UE can simultaneously receive multiple types of UE policies such as URSP and V2X policies from the network side.
  • UE policies such as URSP and V2X policies from the network side.
  • the process of the UE actively requesting the UE policy shown in FIG. 3 is only used for the request of the UE policy (that is, the V2X policy) of the V2X service.
  • FIG. 4 is a schematic flowchart 1 of the method for determining a strategy provided by an embodiment of the application. As shown in FIG. 4, the method for determining a strategy includes the following steps:
  • Step 401 The terminal receives first information sent by the network device, where the first information includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether the terminal is allowed to request the first
  • the indication information of the strategy and the trigger condition of the terminal requesting the first strategy includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether the terminal is allowed to request the first
  • the indication information of the strategy and the trigger condition of the terminal requesting the first strategy includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether the terminal is allowed to request the first
  • the indication information of the strategy and the trigger condition of the terminal requesting the first strategy includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether the terminal is
  • the terminal may be any device capable of communicating with the network, such as a mobile phone, a tablet computer, a notebook, a vehicle-mounted terminal, and a wearable device.
  • the first policy refers to the UE policy
  • the policy type corresponding to the first policy includes at least one of the following: V2X policy, Ultra Reliable & Low Latency Communication (URLLC) policy, Internet of Things ( Cognitive Internet of Things (CIoT) strategy, WLAN selection strategy, URSP strategy, background data transmission strategy.
  • the service type corresponding to the first strategy includes at least one of the following: V2X service, URLLC service, IoT service, and background data transmission service.
  • the policy type can have different names.
  • the policy used for session binding is called URSP policy
  • the policy used for WLAN access point selection is called WLAN selection policy
  • the policy used for car networking is called V2X policy, etc.
  • Business type means that the name of the strategy can be the same, but different strategies or different strategy parts correspond to different services (services used).
  • the part of the strategy used for the Internet of Vehicles corresponds to the V2X business
  • the strategy used for the Internet of Things corresponds to For the Internet of Things business
  • the low-latency and high-reliability strategy corresponds to the URLLC business, etc.
  • the UE policy can be mapped to different types of business.
  • the UE policy is transmitted in the following manner: the network device divides the UE policy into one or more segments and sends it to the terminal, where each segment corresponds to one PSI.
  • the following describes the format of the UE policy content.
  • the format of the UE policy content is used when the network side sends the UE policy to the terminal (see the process shown in Figure 2).
  • the format of the UE policy is shown in Figure 5-1 to Figure 5-1.
  • Figure 5-1 is the information element (IE) of the UE policy section management list (Information Element, IE), including the length of the UE policy section management list and the content of the UE policy section management list.
  • IE information element
  • Figure 5-2 shows the content of the UE policy section management list, including N UE policy section management sublists (management sublist).
  • Figure 5-3 shows the UE policy section management sublist, including PLMN and UE policy section management sublist content.
  • PLMN consists of MCC and MNC.
  • Figure 5-4 shows the content of the UE policy section management sublist, including N instructions.
  • Figure 5-5 shows Instruction, including the length of Instruction content, UPSC and UE policy section content.
  • Figure 5-6 is the UE policy section content, including N UE policy parts; further, Figure 5-7 is the UE policy part, including the UE policy part content length, spare (Spare) bits, UE policy part type, UE Part of the policy.
  • the terminal can perceive the policy type corresponding to the first policy obtained.
  • the terminal can perceive the policy type corresponding to the first policy obtained.
  • the policy content in the first policy includes first indication information, and the first indication information is used to indicate the policy type and/or service type corresponding to the first policy. Further, the policy type field and/or the spare bit field in the policy content in the first policy include the first indication information.
  • the UE policy is composed of a policy identifier and policy content, and first indication information is added to the policy content, and the first indication information includes service information and/or policy type information.
  • the "UE policy part type" field that is, the policy type field
  • the spare bit field that is, the spare bit field
  • the policy identifier in the first policy includes second indication information, and the second indication information is used to indicate the policy type and/or service type corresponding to the first policy. Further, the policy identifier in the first policy includes a PLMN identifier, second indication information, and a policy section code (Policy Section Code, PSC); or, the policy identifier in the first policy includes a PLMN identifier and a PSC, so The PSC includes the second indication information.
  • PSC Policy Section Code
  • each segment will be identified by a PSI.
  • the PSI is composed of the PLMN ID (PLMN ID) and the PSC.
  • the second indication information is added to the PSI.
  • the second indication information includes service information and/or policy type information.
  • PSI is composed of PLMN ID, Service ID and PSC; in Figure 6-2, PSI is composed of PLMN ID and PSC, and PSC further carries Service ID.
  • Manner 3 The value of the policy identifier has a first corresponding relationship with the policy type; the first corresponding relationship is used by the terminal to determine the policy type corresponding to the first policy based on the policy identifier in the first policy and/ Or business type.
  • the policy identifier includes PLMN identifier and PSC.
  • PSI PSI
  • the first information includes a first parameter, and the first parameter is used to indicate the corresponding relationship between the first policy and the policy type and/or service type; the terminal determines the first parameter based on the first parameter.
  • the corresponding relationship between the first policy and the policy type and/or service type includes at least one of the following:
  • the policy identifier includes PLMN identifier and PSC.
  • a new parameter can be added to indicate service information, that is, policy type information.
  • service information that is, policy type information.
  • adding a first parameter is used to indicate that one or more UE policy sections correspond to a specific service.
  • the first parameter may indicate the following information:
  • PSC1-PSC10 correspond to business 1;
  • PSC15, PSC20, PSC24-26 correspond to business 2;
  • PSC50 and PSC65 correspond to service 3.
  • the first parameter may be directly notified to the terminal.
  • the service attribute information of the policy has a second corresponding relationship with the policy type; the second corresponding relationship is used by the terminal to determine the policy type corresponding to the first policy based on the service attribute information in the first policy and / Or business type.
  • the service attribute information includes at least one of the following: Single-Network Slice Selection Assistant Information (S-NSSAI), Data Network Name (DNN), IP address, MAC address, Application ID, session type.
  • the terminal can distinguish the policy type corresponding to the policy according to the existing service attribute information.
  • S-NSSAI of Policy Section-1 corresponds to URLLC services
  • Policy Section-1 is URLLC policy
  • S-NSSAI of Policy Section-2 corresponds to V2X services
  • Policy Section-2 is V2X policy.
  • the network device is a PCF
  • the first information is encapsulated in a container by the PCF and sent to the AMF
  • the container is transparently transmitted to the terminal through the AMF.
  • the container is sent to the terminal using a NAS message through the AMF.
  • the NAS message may be a Downlink NAS Transport (Downlink NAS Transport) message.
  • the terminal can learn the policy type corresponding to the first policy.
  • the terminal requests a policy of a specific policy type (or a specific service) from the network device, it can send the first request message to the network side, and Indicate to update the strategy corresponding to a specific strategy type (or a specific service).
  • the trigger condition for the terminal to request the first policy includes at least one of the following: the first policy expiration time, the first policy effective time, the time when the first request message is initiated, and the time when the first request message is initiated Period, location information where the first request message was initiated.
  • the terminal determines when to send the first request message to the network device according to the trigger condition.
  • the following describes the strategy corresponding to the terminal requesting a specific strategy type (or a specific service) from the network in a targeted manner.
  • FIG. 8 is a schematic diagram of the second flow of the method for determining a strategy according to an embodiment of the application. As shown in FIG. 8, the method for determining a strategy includes the following steps:
  • Step 801 The terminal sends a first request message to the network device, where the first request message includes second information, and the second information is used to instruct the network device to update the target policy type and/or target service type corresponding to Strategy.
  • target policy type and/or “target service type” in the embodiments of the application refer to the policy type and/or service type corresponding to the part of the policy that needs to be updated from the terminal requesting the network side.
  • the network device may send to the terminal indication information of whether the terminal is allowed to request policies and/or indication information of which policies the terminal is allowed to request.
  • the related description of "allowed” can also be replaced with “required”.
  • the second information can be implemented in any of the following ways:
  • the second information includes the target strategy type and/or the strategy identifier corresponding to the target service type.
  • the terminal when the terminal needs to actively update the policy or report the stored PSI during the registration request, the terminal can only report the PSI list corresponding to a specific policy type (or a specific service) when reporting the PSI list, without the need to store the locally stored PSI All PSI lists are reported. For example, the terminal only reports the PSI list corresponding to the V2X policy (V2X service) to the network side, so that the network side only updates the UE Policy (that is, the V2X policy) related to the V2X service.
  • V2X service the V2X policy
  • the UE sends the UE policy request message to the AMF carrying the target policy type and/or the policy identifier corresponding to the target service type (or the policy corresponding to the target service). logo).
  • the second information includes the policy identifier stored by the terminal and at least one of the following information: target policy type and target service type.
  • the terminal when the terminal needs to actively update the policy or report the stored PSI during the registration request, the terminal also reports the PSI corresponding to other services when reporting the PSI list (that is, the terminal reports the PSI list of all services), and also reports the specific policy type (Or specific service information), so that the network side only updates the terminal with a strategy corresponding to a specific policy type (or specific service information).
  • the terminal when the terminal reports all stored PSIs to the network side, it also reports the indication information of the V2X policy (V2X service), so that the network side only updates the UE Policy (that is, the V2X policy) related to the V2X service.
  • the second information includes the target strategy type and/or the target business type.
  • the terminal when the terminal needs to actively update the policy, the terminal reports the target policy type and/or target service type. For example, the terminal reports the indication information of the V2X policy (V2X service) to the network side, so that the network side only updates the UE related to the V2X service Policy (that is, V2X policy).
  • V2X service the V2X policy
  • the UE sends the UE policy request message to the AMF to carry the target policy type (or target service information).
  • the network device is a PCF
  • the second information is packaged in a container by the terminal and sent to the AMF
  • the container is transparently transmitted to the PCF through the AMF.
  • the container is sent to the AMF by using a NAS message through the terminal.
  • the NAS message may be an Uplink NAS Transport (Uplink NAS Transport) message.
  • PSI is also called UPSI
  • PSI itself is composed of PLMN ID and PSC.
  • PSI list When the terminal performs the registration process or the active application for UE policy process, it will carry its own stored PSI list (PSI list) in the NAS message sent to the network. The network side also knows which policies the terminal has stored, and based on this Update.
  • the compilation format of the PSI list is shown in Figure 9-1 and Figure 9-2.
  • Figure 9-1 is the information unit of the UPSI list, including the length information of the PSI list content and N UPSI sublists (UPSI sublists); further, the figure 9-2 is the UPSI sublist, including the length information of the UPSI sublist, PLMN and UPSC, where PLMN is composed of MCC and MNC.
  • the policy information will contain measurement type information (or service information), so as to help the terminal determine which policy type the policy belongs to, so that the network can be specifically requested to implement a specific policy type policy. Update.
  • the technical solutions of the embodiments of the present application make full use of existing parameters and processes, and have little impact on the existing system.
  • FIG. 10 is a schematic diagram 1 of the structural composition of a policy determining apparatus provided by an embodiment of the application. As shown in FIG. 10, the policy determining apparatus includes:
  • the receiving unit 1001 is configured to receive first information sent by a network device, where the first information includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether terminal requests are allowed.
  • the indication information of the first strategy and the trigger condition for the terminal to request the first strategy is configured to receive first information sent by a network device, where the first information includes at least one of the following: a first policy, a policy type corresponding to the first policy, a service type corresponding to the first policy, and whether terminal requests are allowed.
  • the policy content in the first policy includes first indication information, and the first indication information is used to indicate the policy type and/or service type corresponding to the first policy.
  • the policy type field and/or the spare bit field in the policy content in the first policy includes the first indication information.
  • the policy identifier in the first policy includes second indication information, and the second indication information is used to indicate the policy type and/or service type corresponding to the first policy.
  • the policy identifier in the first policy includes a PLMN identifier, second indication information, and PSC; or,
  • the policy identifier in the first policy includes a PLMN identifier and a PSC, and the PSC includes the second indication information.
  • the value of the strategy identifier has a first corresponding relationship with the strategy type
  • the first correspondence is used by the terminal to determine the policy type and/or service type corresponding to the first policy based on the policy identifier in the first policy.
  • the first information includes a first parameter, and the first parameter is used to indicate the correspondence between the first policy and the policy type and/or service type;
  • the first parameter is used by the terminal to determine the policy type and/or service type corresponding to the first policy.
  • the corresponding relationship between the first policy and the policy type and/or service type includes at least one of the following:
  • the policy identifier includes a PLMN identifier and a PSC.
  • the business attribute information of the strategy has a second correspondence with the strategy type
  • the second correspondence is used by the terminal to determine the policy type and/or service type corresponding to the first policy based on the service attribute information in the first policy.
  • the service attribute information includes at least one of the following: S-NSSAI, DNN, IP address, MAC address, application identifier, and session type.
  • the trigger condition for the terminal to request the first strategy includes at least one of the following:
  • the first policy expiration time The first policy expiration time, the first policy effective time, the time of initiating the first request message, the time period of initiating the first request message, and the location information where the first request message is initiated.
  • the device further includes:
  • the sending unit 1002 is configured to send a first request message to the network device, where the first request message includes second information, and the second information is used to instruct the network device to update the target policy type and/or target service type The corresponding strategy.
  • the second information includes a target strategy type and/or a strategy identifier corresponding to the target service type.
  • the second information includes a policy identifier stored by the terminal and at least one of the following information: a target policy type and a target service type.
  • the second information includes a target strategy type and/or a target service type.
  • the network device is a PCF
  • the first information is encapsulated in a container by the PCF and sent to the AMF
  • the container is transparently transmitted to the terminal through the AMF.
  • the container is sent to the terminal using a NAS message through the AMF.
  • the network device is a PCF
  • the second information is encapsulated in a container by the terminal and sent to the AMF
  • the container is transparently transmitted to the PCF through the AMF.
  • the container is sent to the AMF by using a NAS message through the terminal.
  • the strategy type corresponding to the first strategy includes at least one of the following:
  • V2X strategy high reliability and low latency URLLC strategy, IoT CIoT strategy, WLAN selection strategy, URSP strategy, background data transmission strategy;
  • the service type corresponding to the first strategy includes at least one of the following: V2X service, URLLC service, IoT service, and background data transmission service.
  • FIG. 11 is a schematic diagram 2 of the structural composition of the policy determining apparatus provided by an embodiment of the application. As shown in FIG. 11, the policy determining apparatus includes:
  • the sending unit 1101 is configured to send a first request message to the network device, where the first request message includes second information, and the second information is used to instruct the network device to update the target policy type and/or target service type The corresponding strategy.
  • the second information includes a target strategy type and/or a strategy identifier corresponding to the target service type.
  • the second information includes a policy identifier stored by the terminal and at least one of the following information: a target policy type and a target service type.
  • the second information includes a target strategy type and/or a target service type.
  • the network device is a PCF
  • the second information is encapsulated in a container by the terminal and sent to the AMF
  • the container is transparently transmitted to the PCF through the AMF.
  • the container is sent to the AMF by using a NAS message through the terminal.
  • FIG. 12 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application.
  • the communication device may be a terminal or a network device.
  • the communication device 600 shown in FIG. 12 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
  • the communication device 600 may further include a memory 620.
  • the processor 610 may call and run a computer program from the memory 620 to implement the method in the embodiment of the present application.
  • the memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.
  • the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices, or receive other devices. Information or data sent by the device.
  • the transceiver 630 may include a transmitter and a receiver.
  • the transceiver 630 may further include an antenna, and the number of antennas may be one or more.
  • the communication device 600 may specifically be a network device in an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For brevity, details are not repeated here. .
  • the communication device 600 may specifically be a mobile terminal/terminal according to an embodiment of the application, and the communication device 600 may implement the corresponding procedures implemented by the mobile terminal/terminal in each method of the embodiments of the application. For the sake of brevity, This will not be repeated here.
  • FIG. 13 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the chip 700 shown in FIG. 13 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.
  • the chip 700 may further include a memory 720.
  • the processor 710 may call and run a computer program from the memory 720 to implement the method in the embodiment of the present application.
  • the memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.
  • the chip 700 may further include an input interface 730.
  • the processor 710 may control the input interface 730 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
  • the chip 700 may further include an output interface 740.
  • the processor 710 can control the output interface 740 to communicate with other devices or chips, and specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in the various methods of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the network device in the various methods of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal in the embodiments of the present application, and the chip can implement the corresponding procedures implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. Repeat.
  • the chip mentioned in the embodiment of the present application may also be referred to as a system-level chip, a system-on-chip, a system-on-chip, or a system-on-chip.
  • FIG. 14 is a schematic block diagram of a communication system 900 according to an embodiment of the present application.
  • the communication system 900 includes a terminal 910 and a network device 920.
  • the terminal 910 may be used to implement the corresponding functions implemented by the terminal in the foregoing method
  • the network device 920 may be used to implement the corresponding functions implemented by the network device in the foregoing method.
  • details are not described herein again.
  • the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the aforementioned processor may be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (Field Programmable Gate Array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM DDR SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • Synchlink DRAM SLDRAM
  • DR RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiment of the present application is intended to include but not limited to these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program causes the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer-readable storage medium may be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application, for It's concise, so I won't repeat it here.
  • the embodiments of the present application also provide a computer program product, including computer program instructions.
  • the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program product can be applied to the mobile terminal/terminal in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding procedures implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application, for the sake of brevity , I won’t repeat it here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program runs on the computer, the computer is caused to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • I won’t repeat it here.
  • the computer program can be applied to the mobile terminal/terminal in the embodiments of the present application.
  • the computer program runs on the computer, the computer can execute the corresponding methods implemented by the mobile terminal/terminal in the various methods of the embodiments of the present application. For the sake of brevity, the process will not be repeated here.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.
  • each unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of this application essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种策略确定方法及装置、终端,该方法包括:终端接收网络设备发送的第一信息,所述第一信息包括以下至少之一:第一策略、第一策略对应的策略类型、第一策略对应的业务类型、是否允许终端请求第一策略的指示信息、终端请求第一策略的触发条件。

Description

一种策略确定方法及装置、终端 技术领域
本申请实施例涉及移动通信技术领域,具体涉及一种策略确定方法及装置、终端。
背景技术
网络给终端下发用户设备策略(User Equipment policy,UE policy)时,将UE policy分为一个或多个分段(Section)进行传输,其中,每一个分段对应一个标识,即策略分段标识(Policy Section Identifier,PSI)。UE policy的类型具有多种,终端接收UE policy时,无法区分每个分段对应哪一种策略类型。
发明内容
本申请实施例提供一种策略确定方法及装置、终端、网络设备。
本申请实施例提供的策略确定方法,包括:
终端接收网络设备发送的第一信息,所述第一信息包括以下至少之一:第一策略、第一策略对应的策略类型、第一策略对应的业务类型、是否允许终端请求第一策略的指示信息、终端请求第一策略的触发条件。
本申请实施例提供的策略确定方法,包括:
终端向所述网络设备发送第一请求消息,所述第一请求消息包括第二信息,所述第二信息用于指示所述网络设备更新目标策略类型和/或目标业务类型对应的策略。
本申请实施例提供的策略确定装置,包括:
接收单元,用于接收网络设备发送的第一信息,所述第一信息包括以下至少之一:第一策略、第一策略对应的策略类型、第一策略对应的业务类型、是否允许终端请求第一策略的指示信息、终端请求第一策略的触发条件。
本申请实施例提供的策略确定装置,包括:
发送单元,用于向所述网络设备发送第一请求消息,所述第一请求消息包括第二信息,所述第二信息用于指示所述网络设备更新目标策略类型和/或目标业务类型对应的策略。
本申请实施例提供的终端,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,执行上述的策略确定方法。
本申请实施例提供的芯片,用于实现上述的策略确定方法。
具体地,该芯片包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有该芯片的设备执行上述的策略确定方法。
本申请实施例提供的计算机可读存储介质,用于存储计算机程序,该计算机程序使得计算机执行上述的策略确定方法。
本申请实施例提供的计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行上述的策略确定方法。
本申请实施例提供的计算机程序,当其在计算机上运行时,使得计算机执行上述 的策略确定方法。
通过上述技术方案,终端接收网络设备发送的第一信息,所述第一信息包括以下至少之一:第一策略、第一策略对应的策略类型、第一策略对应的业务类型、是否允许终端请求第一策略的指示信息、终端请求第一策略的触发条件;如此,可以使得终端感知策略属于何种策略类型,从而可以有针对性的请求网络侧更新特定策略类型的策略。
附图说明
此处所说明的附图用来提供对本申请的进一步理解,构成本申请的一部分,本申请的示意性实施例及其说明用于解释本申请,并不构成对本申请的不当限定。在附图中:
图1是本申请实施例提供的一种通信系统架构的示意性图;
图2是本申请实施例提供的UE policy的配置流程图;
图3是本申请实施例提供的UE主动请求UE policy的流程图;
图4是本申请实施例提供的策略确定方法的流程示意图一;
图5-1是UE policy section management list的信息单元的示意图;
图5-2是UE policy section management list的内容的示意图;
图5-3是UE policy section management sublist的示意图;
图5-4是UE policy section management sublist内容的示意图;
图5-5是Instruction的示意图;
图5-6是UE policy section内容的示意图;
图5-7是UE policy部分的示意图;
图6-1是本申请实施例提供的PSI的结构示意图一;
图6-2是本申请实施例提供的PSI的结构示意图二;
图7是本申请实施例提供的PSI与业务类型的对应关系图;
图8是本申请实施例提供的策略确定方法的流程示意图二;
图9-1是UPSI列表的信息单元的示意图;
图9-2是UPSI子列表的示意图;
图10是本申请实施例提供的策略确定装置的结构组成示意图一;
图11是本申请实施例提供的策略确定装置的结构组成示意图二;
图12是本申请实施例提供的一种通信设备示意性结构图;
图13是本申请实施例的芯片的示意性结构图;
图14是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统,例如:全球移动通讯(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)系统、LTE频分双工(Frequency Division Duplex,FDD)系统、LTE 时分双工(Time Division Duplex,TDD)、通用移动通信系统(Universal Mobile Telecommunication System,UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access,WiMAX)通信系统或5G系统等。
示例性的,本申请实施例应用的通信系统100如图1所示。该通信系统100可以包括网络设备110,网络设备110可以是与终端120(或称为通信终端、终端)通信的设备。网络设备110可以为特定的地理区域提供通信覆盖,并且可以与位于该覆盖区域内的终端进行通信。可选地,该网络设备110可以是GSM系统或CDMA系统中的基站(Base Transceiver Station,BTS),也可以是WCDMA系统中的基站(NodeB,NB),还可以是LTE系统中的演进型基站(Evolutional Node B,eNB或eNodeB),或者是云无线接入网络(Cloud Radio Access Network,CRAN)中的无线控制器,或者该网络设备可以为移动交换中心、中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器、5G网络中的网络侧设备或者未来演进的公共陆地移动网络(Public Land Mobile Network,PLMN)中的网络设备等。
该通信系统100还包括位于网络设备110覆盖范围内的至少一个终端120。作为在此使用的“终端”包括但不限于经由有线线路连接,如经由公共交换电话网络(Public Switched Telephone Networks,PSTN)、数字用户线路(Digital Subscriber Line,DSL)、数字电缆、直接电缆连接;和/或另一数据连接/网络;和/或经由无线接口,如,针对蜂窝网络、无线局域网(Wireless Local Area Network,WLAN)、诸如DVB-H网络的数字电视网络、卫星网络、AM-FM广播发送器;和/或另一终端的被设置成接收/发送通信信号的装置;和/或物联网(Internet of Things,IoT)设备。被设置成通过无线接口通信的终端可以被称为“无线通信终端”、“无线终端”或“移动终端”。移动终端的示例包括但不限于卫星或蜂窝电话;可以组合蜂窝无线电电话与数据处理、传真以及数据通信能力的个人通信系统(Personal Communications System,PCS)终端;可以包括无线电电话、寻呼机、因特网/内联网接入、Web浏览器、记事簿、日历以及/或全球定位系统(Global Positioning System,GPS)接收器的PDA;以及常规膝上型和/或掌上型接收器或包括无线电电话收发器的其它电子装置。终端可以指接入终端、用户设备(User Equipment,UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、无线本地环路(Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端或者未来演进的PLMN中的终端等。
可选地,终端120之间可以进行终端直连(Device to Device,D2D)通信。
可选地,5G系统或5G网络还可以称为新无线(New Radio,NR)系统或NR网络。
图1示例性地示出了一个网络设备和两个终端,可选地,该通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端,本申请实施例对此不做限定。
可选地,该通信系统100还可以包括网络控制器、移动管理实体等其他网络实体,本申请实施例对此不作限定。
应理解,本申请实施例中网络/系统中具有通信功能的设备可称为通信设备。以图1示出的通信系统100为例,通信设备可包括具有通信功能的网络设备110和终端120,网络设备110和终端120可以为上文所述的具体设备,此处不再赘述;通信设备还可包括通信系统100中的其他设备,例如网络控制器、移动管理实体等其他网络实体,本申请实施例中对此不做限定。
应理解,本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
为便于理解本申请实施例的技术方案,以下先对本申请实施例涉及到的几种类型的UE policy进行描述。
1)WLAN选择策略(WLAN Selection Policy,WLANSP)
WLANSP包含多个规则,WLANSP中规则称为WLANSP rule,WLANSP rule用于UE选择哪一个WLAN接入点时使用。
2)UE路由选择策略(UE Route Selection Policy,URSP)
URSP包含多个规则,URSP中的规则称为URSP Rule,每一个URSP Rule由业务描述(Traffic Descriptor)和一组路由选择描述(Route Selection Descriptor,RSD)组成。URSP的相关的内容如下表1和表2所示:
Figure PCTCN2019079141-appb-000001
表1:URSP Rule
Figure PCTCN2019079141-appb-000002
表2:RSD
3)V2X策略
UE policy的类型除了包括URSP、WLANSP以外,还可以在用途上进行区分,比如有些UE policy用于eMBB业务,有些UE policy用于V2X业务。进一步,V2X策略分为PC5策略和Uu接口策略。
UE policy的配置通过UE配置更新(UE Configuration Update,UCU)流程实现,如图2所示,该流程包括以下步骤:
步骤201:策略控制功能网元(Policy Control Function,PCF)决定更新UE policy。
步骤202:PCF将要更新的UE policy放在一个容器(Container)里,发送给核心接入和移动性管理网元(Core Access and Mobility Management Function,AMF)。
步骤203:AMF使用NAS消息将容器直接转发给UE。
3GPP规定了UE主动请求UE policy的流程,如图3所示,该流程包括以下步骤:
步骤301:UE向AMF发送UE policy请求消息。
步骤302:AMF向PCF发送UE policy控制更新消息。
步骤303:UE与PCF之间进行UE policy的配置流程。
这里,UE policy的配置流程参照图2所示的流程。
需要说明的是,UE可以同时从网络侧接收URSP、V2X策略等多种类型的UE policy。另一方面。图3所示的UE主动请求UE policy的流程只用于V2X业务的UE policy(即V2X策略)的请求。
图4为本申请实施例提供的策略确定方法的流程示意图一,如图4所示,所述策略确定方法包括以下步骤:
步骤401:终端接收网络设备发送的第一信息,所述第一信息包括以下至少之一:第一策略、第一策略对应的策略类型、第一策略对应的业务类型、是否允许终端请求第一策略的指示信息、终端请求第一策略的触发条件。
本申请实施例中,所述终端可以是手机、平板电脑、笔记本、车载终端、可穿戴式 设备等任意能够与网络进行通信的设备。
本申请实施例中,第一策略是指UE policy,所述第一策略对应的策略类型包括以下至少之一:V2X策略、高可靠低时延(Ultra Reliable&Low Latency Communication,URLLC)策略、物联网(Cognitive Internet of Things,CIoT)策略、WLAN选择策略、URSP策略、背景数据传输策略。所述第一策略对应的业务类型包括以下至少之一:V2X业务、URLLC业务、IoT业务、背景数据传输业务。
需要说明的是,策略类型可以是策略的名称不同,比如用于会话绑定的策略叫URSP策略、用于WLAN接入点选择的策略叫WLAN选择策略、用于车联网的策略叫V2X策略等。业务类型是指策略名称可以相同,但不同策略或不同的策略部分对应的业务(被用于的业务)不同,比如用于车联网的那部分策略对应于V2X业务、用于物联网的策略对应于物联网业务、用于低时延高可靠的策略对应于URLLC业务等,可以将UE policy对应到不同种类的业务。
本申请实施例中,UE policy通过以下方式传输:网络设备将UE policy分为一个或多个分段发送给终端,其中,每一个分段对应一个PSI。以下对UE policy内容的编制格式进行说明,UE policy内容的编制格式用于网络侧发送给终端UE policy时使用(见图2所示的流程),UE policy的编制格式如图5-1至图5-7所示,其中,图5-1为UE policy section管理列表(management list)的信息单元(Information Element,IE),包括UE policy section management list的长度和UE policy section management list的内容。进一步,图5-2为UE policy section management list的内容,包括N个UE policy section管理子列表(management sublist)。进一步,图5-3为UE policy section management sublist,包括PLMN和UE policy section management sublist内容,其中,PLMN有MCC和MNC组成。进一步,图5-4为UE policy section management sublist内容,包括N个Instruction。进一步,图5-5为Instruction,包括Instruction内容长度、UPSC和UE policy section内容。进一步,图5-6为UE policy section内容,包括N个UE policy部分;进一步,图5-7为UE policy部分,包括UE policy部分内容长度、备用(Spare)比特位、UE policy部分类型、UE policy部分内容。
本申请实施例中,终端能够感知获得的第一策略对应的策略类型,为实现此目的,有如下几种实现方式:
方式一:所述第一策略中的策略内容中包括第一指示信息,所述第一指示信息用于指示所述第一策略对应的策略类型和/或业务类型。进一步,所述第一策略中的策略内容中的策略类型字段和/或备用比特位字段包括所述第一指示信息。
举个例子:UE policy由策略标识和策略内容组成,在策略内容中添加第一指示信息,所述第一指示信息包括业务信息和/或策略类型信息。参照图5-7,可以利用“UE policy part type”字段(即策略类型字段)和/或spare比特位字段(即备用比特位字段)中增加新的值来区分策略类型。
方式二:所述第一策略中的策略标识中包括第二指示信息,所述第二指示信息用于指示所述第一策略对应的策略类型和/或业务类型。进一步,所述第一策略中的策略标识包括PLMN标识、第二指示信息和策略分段码(Policy Section Code,PSC);或者,所述第一策略中的策略标识包括PLMN标识和PSC,所述PSC包含所述第二指示信息。
具体地,考虑到UE policy会划分成一个或多个分段,每一个分段会由一个PSI来标识,PSI是由PLMN标识(PLMN ID)和PSC组成的,新增加第二指示信息到PSI中,所述第二指示信息包括业务信息和/或策略类型信息。参照图6-1和图6-2,图6-1中,PSI由PLMN ID、业务标识(Service ID)和PSC组成;图6-2中,PSI由PLMN ID 和PSC组成,PSC进一步携带Service ID。
方式三:策略标识的取值与策略类型具有第一对应关系;所述第一对应关系用于所述终端基于所述第一策略中的策略标识确定所述第一策略对应的策略类型和/或业务类型。
这里,所述策略标识包括PLMN标识和PSC。
举个例子:可以通过协议约定UE policy的PSI的取值范围对应于特定的业务,也即对应特定的策略类型。参照图7,对于PSI(PLMN ID+PSC),约定其不同的取值对应不同的业务类型,PSC=1-30对应业务1,PSC=31-50对应业务2,PSC=51-80对应业务3。
方式四:所述第一信息包括第一参数,所述第一参数用于指示第一策略与策略类型和/或业务类型的对应关系;所述终端基于所述第一参数确定所述第一策略对应的策略类型和/或业务类型。
这里,所述第一策略与策略类型和/或业务类型的对应关系包括以下至少之一:
至少一个策略标识与策略类型和/或业务类型之间的对应关系;
至少一个策略规则与策略类型和/或业务类型之间的对应关系;
至少一个策略分段与策略类型和/或业务类型之间的对应关系。
这里,所述策略标识包括PLMN标识和PSC。
这里,可以添加新的参数指示业务信息,也即策略类型信息。比如:添加第一参数用于指示一个或多个UE policy Section对应于某一特定业务,在一个例子中,第一参数可以指示以下信息:
PSC1-PSC10对应业务1;
PSC15、PSC20、PSC24-26对应业务2;
PSC50、PSC65对应业务3。
在网络设备下发给UE Policy给终端时,可以直接将第一参数通知给终端。
方式五:策略的业务属性信息与策略类型具有第二对应关系;所述第二对应关系用于所述终端基于所述第一策略中的业务属性信息确定所述第一策略对应的策略类型和/或业务类型。进一步,所述业务属性信息包括以下至少之一:单网络切片选择辅助信息(Single-Network Slice Selection Assistant Information,S-NSSAI)、数据网络名(Data Network Name,DNN)、IP地址、MAC地址、应用标识、会话类型。
具体地,由于策略本身携带有S-NSSAI、DNN等业务属性信息,终端可以根据现有的业务属性信息来区分出策略对应的策略类型。
比如:Policy Section-1的S-NSSAI对应URLLC业务,Policy Section-1为URLLC策略,Policy Section-2的S-NSSAI对应V2X业务,Policy Section-2为V2X策略。
本申请实施例中,所述网络设备为PCF,所述第一信息由PCF封装在容器中发送给AMF,所述容器通过所述AMF透传给所述终端。进一步,所述容器通过所述AMF采用NAS消息发送给所述终端。这里,NAS消息可以是下行NAS传输(Downlink NAS Transport)消息。
通过本申请实施例上述技术方案,终端可以获知第一策略对应的策略类型,当终端向网络设备请求特定策略类型(或者说特定业务)的策略时,可以向网络侧发送第一请求消息,并指示更新特定策略类型(或者说特定业务)对应的策略。
本申请实施例中,所述终端请求第一策略的触发条件包括以下至少之一:第一策略到期时间、第一策略有效时间、发起第一请求消息的时间、发起第一请求消息的时间周期、发起第一请求消息的位置信息。所述终端根据触发条件确定何时向网络设备发送第一请求消息。
以下对终端有针对性的向网络请求特定策略类型(或者说特定业务)对应的策略进行描述。
图8为本申请实施例提供的策略确定方法的流程示意图二,如图8所示,所述策略确定方法包括以下步骤:
步骤801:终端向所述网络设备发送第一请求消息,所述第一请求消息包括第二信息,所述第二信息用于指示所述网络设备更新目标策略类型和/或目标业务类型对应的策略。
需要说明的是,本申请实施例中的“目标策略类型”和/或“目标业务类型”指的是终端向网络侧请求需要更新的那部分策略对应的策略类型和/或业务类型。
需要说明的是,终端向所述网络设备发送第一请求消息之前,网络设备可以向终端发送是否允许终端请求策略的指示信息和/或允许终端请求哪些策略的指示信息。这里,“允许”的相关描述也可以替换成“需要”。
本申请实施例中,所述第二信息可以通过以下任意一种方式来实现:
方式一:所述第二信息包括目标策略类型和/或目标业务类型对应的策略标识。
具体地,当终端需要主动更新策略或在注册请求时上报存储的PSI时,终端在上报PSI list时可以只上报特定策略类型(或者是特定业务)对应的PSI list,而不需要将本地存储的全部PSI list都上报。比如终端只上报V2X策略(V2X业务)对应的PSI list给网络侧,这样网络侧只会更新V2X业务相关的UE Policy(即V2X策略)。
参照图3所示的UE主动请求UE policy的流程,在步骤301中,UE向AMF发送UE policy请求消息中携带目标策略类型和/或目标业务类型对应的策略标识(或者是目标业务对应的策略标识)。
方式二:所述第二信息包括所述终端存储的策略标识和以下至少一种信息:目标策略类型、目标业务类型。
具体地,当终端需要主动更新策略或在注册请求时上报存储的PSI时,终端上报PSI list时也把其他业务对应的PSI上报上去(即终端上报全部业务的PSI list),同时上报特定策略类型(或者是特定业务信息),这样网络侧只给终端更新特定策略类型(或者是特定业务信息)对应的策略。比如终端向网络侧上报了全部存储的PSI的同时,还上报V2X策略(V2X业务)的指示信息,这样网络侧只会更新V2X业务相关的UE Policy(即V2X策略)。
方式三:所述第二信息包括目标策略类型和/或目标业务类型。
具体地,当终端需要主动更新策略时,终端上报目标策略类型和/或目标业务类型,比如终端向网络侧上报V2X策略(V2X业务)的指示信息,这样网络侧只会更新V2X业务相关的UE Policy(即V2X策略)。
参照图3所示的UE主动请求UE policy的流程,在步骤301中,UE向AMF发送UE policy请求消息中携带目标策略类型(或者是目标业务信息)。
本申请实施例中,所述网络设备为PCF,所述第二信息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。进一步,所述容器通过所述终端采用NAS消息发送给所述AMF。这里,NAS消息可以是上行NAS传输(Uplink NAS Transport)消息。
上述方案中,PSI也叫UPSI,PSI本身由PLMN ID和PSC组成。当终端执行注册流程或执行主动申请UE policy流程时,会在发给网络的NAS消息中携带自己存储的PSI列表(PSI list),网络侧也就知道该终端已经存储了哪些策略,并据此进行更新。PSI list的编制格式如图9-1和图9-2所示,图9-1为UPSI列表的信息单元,包括PSI list内容的长度信息和N个UPSI子列表(UPSI sublist);进一步,图9-2为 UPSI sublist,包括UPSI sublist的长度信息、PLMN和UPSC,其中,PLMN由MCC和MNC组成。
本申请实施例的技术方案,策略信息中将包含测量类型信息(或者说业务信息),从而有助于终端判断策略属于哪种策略类型,从而可以针对性的请求网络进行特定策略类型的策略的更新。本申请实施例的技术方案充分使用了现有参数和流程,对现有系统的影响较小。
需要说明的是,上述图8相关的技术方案与图4相关的技术方案可以结合在一起进行实施,也可以独立进行实施。
图10为本申请实施例提供的策略确定装置的结构组成示意图一,如图10所示,所述策略确定装置包括:
接收单元1001,用于接收网络设备发送的第一信息,所述第一信息包括以下至少之一:第一策略、第一策略对应的策略类型、第一策略对应的业务类型、是否允许终端请求第一策略的指示信息、终端请求第一策略的触发条件。
在一实施方式中,所述第一策略中的策略内容中包括第一指示信息,所述第一指示信息用于指示所述第一策略对应的策略类型和/或业务类型。
在一实施方式中,所述第一策略中的策略内容中的策略类型字段和/或备用比特位字段包括所述第一指示信息。
在一实施方式中,所述第一策略中的策略标识中包括第二指示信息,所述第二指示信息用于指示所述第一策略对应的策略类型和/或业务类型。
在一实施方式中,所述第一策略中的策略标识包括PLMN标识、第二指示信息和PSC;或者,
所述第一策略中的策略标识包括PLMN标识和PSC,所述PSC包含所述第二指示信息。
在一实施方式中,策略标识的取值与策略类型具有第一对应关系;
所述第一对应关系用于所述终端基于所述第一策略中的策略标识确定所述第一策略对应的策略类型和/或业务类型。
在一实施方式中,所述第一信息包括第一参数,所述第一参数用于指示第一策略与策略类型和/或业务类型的对应关系;
所述第一参数用于所述终端确定所述第一策略对应的策略类型和/或业务类型。
在一实施方式中,所述第一策略与策略类型和/或业务类型的对应关系包括以下至少之一:
至少一个策略标识与策略类型和/或业务类型之间的对应关系;
至少一个策略规则与策略类型和/或业务类型之间的对应关系;
至少一个策略分段与策略类型和/或业务类型之间的对应关系。
在一实施方式中,所述策略标识包括PLMN标识和PSC。
在一实施方式中,策略的业务属性信息与策略类型具有第二对应关系;
所述第二对应关系用于所述终端基于所述第一策略中的业务属性信息确定所述第一策略对应的策略类型和/或业务类型。
在一实施方式中,所述业务属性信息包括以下至少之一:S-NSSAI、DNN、IP地址、MAC地址、应用标识、会话类型。
在一实施方式中,所述终端请求第一策略的触发条件包括以下至少之一:
第一策略到期时间、第一策略有效时间、发起第一请求消息的时间、发起第一请求消息的时间周期、发起第一请求消息的位置信息。
在一实施方式中,所述装置还包括:
发送单元1002,用于向所述网络设备发送第一请求消息,所述第一请求消息包括第二信息,所述第二信息用于指示所述网络设备更新目标策略类型和/或目标业务类型对应的策略。
在一实施方式中,所述第二信息包括目标策略类型和/或目标业务类型对应的策略标识。
在一实施方式中,所述第二信息包括所述终端存储的策略标识和以下至少一种信息:目标策略类型、目标业务类型。
在一实施方式中,所述第二信息包括目标策略类型和/或目标业务类型。
在一实施方式中,所述网络设备为PCF,所述第一信息由PCF封装在容器中发送给AMF,所述容器通过所述AMF透传给所述终端。
在一实施方式中,所述容器通过所述AMF采用NAS消息发送给所述终端。
在一实施方式中,所述网络设备为PCF,所述第二信息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
在一实施方式中,所述容器通过所述终端采用NAS消息发送给所述AMF。
在一实施方式中,所述第一策略对应的策略类型包括以下至少之一:
V2X策略、高可靠低时延URLLC策略、物联网CIoT策略、WLAN选择策略、URSP策略、背景数据传输策略;
所述第一策略对应的业务类型包括以下至少之一:V2X业务、URLLC业务、IoT业务、背景数据传输业务。
本领域技术人员应当理解,本申请实施例的上述MCS配置装置的相关描述可以参照本申请实施例的策略确定方法的相关描述进行理解。
图11为本申请实施例提供的策略确定装置的结构组成示意图二,如图11所示,所述策略确定装置包括:
发送单元1101,用于向所述网络设备发送第一请求消息,所述第一请求消息包括第二信息,所述第二信息用于指示所述网络设备更新目标策略类型和/或目标业务类型对应的策略。
在一实施方式中,所述第二信息包括目标策略类型和/或目标业务类型对应的策略标识。
在一实施方式中,所述第二信息包括所述终端存储的策略标识和以下至少一种信息:目标策略类型、目标业务类型。
在一实施方式中,所述第二信息包括目标策略类型和/或目标业务类型。
在一实施方式中,所述网络设备为PCF,所述第二信息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
在一实施方式中,所述容器通过所述终端采用NAS消息发送给所述AMF。
本领域技术人员应当理解,本申请实施例的上述MCS配置装置的相关描述可以参照本申请实施例的策略确定方法的相关描述进行理解。
图12是本申请实施例提供的一种通信设备600示意性结构图。该通信设备可以是终端,也可以是网络设备,图12所示的通信设备600包括处理器610,处理器610可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图12所示,通信设备600还可以包括存储器620。其中,处理器610可以从存储器620中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器620可以是独立于处理器610的一个单独的器件,也可以集成在处理器610中。
可选地,如图12所示,通信设备600还可以包括收发器630,处理器610可以控制 该收发器630与其他设备进行通信,具体地,可以向其他设备发送信息或数据,或接收其他设备发送的信息或数据。
其中,收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线,天线的数量可以为一个或多个。
可选地,该通信设备600具体可为本申请实施例的网络设备,并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该通信设备600具体可为本申请实施例的移动终端/终端,并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程,为了简洁,在此不再赘述。
图13是本申请实施例的芯片的示意性结构图。图13所示的芯片700包括处理器710,处理器710可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图13所示,芯片700还可以包括存储器720。其中,处理器710可以从存储器720中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器720可以是独立于处理器710的一个单独的器件,也可以集成在处理器710中。
可选地,该芯片700还可以包括输入接口730。其中,处理器710可以控制该输入接口730与其他设备或芯片进行通信,具体地,可以获取其他设备或芯片发送的信息或数据。
可选地,该芯片700还可以包括输出接口740。其中,处理器710可以控制该输出接口740与其他设备或芯片进行通信,具体地,可以向其他设备或芯片输出信息或数据。
可选地,该芯片可应用于本申请实施例中的网络设备,并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该芯片可应用于本申请实施例中的移动终端/终端,并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程,为了简洁,在此不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
图14是本申请实施例提供的一种通信系统900的示意性框图。如图14所示,该通信系统900包括终端910和网络设备920。
其中,该终端910可以用于实现上述方法中由终端实现的相应的功能,以及该网络设备920可以用于实现上述方法中由网络设备实现的相应的功能为了简洁,在此不再赘述。
应理解,本申请实施例的处理器可能是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor,DSP)、专用集成电路(Application Specific Integrated Circuit,ASIC)、现成可编程门阵列(Field Programmable Gate Array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合 其硬件完成上述方法的步骤。
可以理解,本申请实施例中的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(Static RAM,SRAM)、动态随机存取存储器(Dynamic RAM,DRAM)、同步动态随机存取存储器(Synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)。应注意,本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解,上述存储器为示例性但不是限制性说明,例如,本申请实施例中的存储器还可以是静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synch link DRAM,SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)等等。也就是说,本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质,用于存储计算机程序。
可选的,该计算机可读存储介质可应用于本申请实施例中的网络设备,并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机可读存储介质可应用于本申请实施例中的移动终端/终端,并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程,为了简洁,在此不再赘述。
本申请实施例还提供了一种计算机程序产品,包括计算机程序指令。
可选的,该计算机程序产品可应用于本申请实施例中的网络设备,并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机程序产品可应用于本申请实施例中的移动终端/终端,并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程,为了简洁,在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的,该计算机程序可应用于本申请实施例中的网络设备,当该计算机程序在计算机上运行时,使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机程序可应用于本申请实施例中的移动终端/终端,当该计算机程序在计算机上运行时,使得计算机执行本申请实施例的各个方法中由移动终端/终端实现的相应流程,为了简洁,在此不再赘述。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元 及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,)ROM、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应所述以权利要求的保护范围为准。

Claims (61)

  1. 一种策略确定方法,所述方法包括:
    终端接收网络设备发送的第一信息,所述第一信息包括以下至少之一:第一策略、第一策略对应的策略类型、第一策略对应的业务类型、是否允许终端请求第一策略的指示信息、终端请求第一策略的触发条件。
  2. 根据权利要求1所述的方法,其中,所述第一策略中的策略内容中包括第一指示信息,所述第一指示信息用于指示所述第一策略对应的策略类型和/或业务类型。
  3. 根据权利要求2所述的方法,其中,所述第一策略中的策略内容中的策略类型字段和/或备用比特位字段包括所述第一指示信息。
  4. 根据权利要求1所述的方法,其中,所述第一策略中的策略标识中包括第二指示信息,所述第二指示信息用于指示所述第一策略对应的策略类型和/或业务类型。
  5. 根据权利要求4所述的方法,其中,
    所述第一策略中的策略标识包括公共陆地移动网络PLMN标识、第二指示信息和策略分段码PSC;或者,
    所述第一策略中的策略标识包括PLMN标识和PSC,所述PSC包含所述第二指示信息。
  6. 根据权利要求1所述的方法,其中,策略标识的取值与策略类型具有第一对应关系;
    所述第一对应关系用于所述终端基于所述第一策略中的策略标识确定所述第一策略对应的策略类型和/或业务类型。
  7. 根据权利要求1所述的方法,其中,所述第一信息包括第一参数,所述第一参数用于指示第一策略与策略类型和/或业务类型的对应关系;所述终端基于所述第一参数确定所述第一策略对应的策略类型和/或业务类型。
  8. 根据权利要求7所述的方法,其中,所述第一策略与策略类型和/或业务类型的对应关系包括以下至少之一:
    至少一个策略标识与策略类型和/或业务类型之间的对应关系;
    至少一个策略规则与策略类型和/或业务类型之间的对应关系;
    至少一个策略分段与策略类型和/或业务类型之间的对应关系。
  9. 根据权利要求6至8中任一项所述的方法,其中,所述策略标识包括PLMN标识和PSC。
  10. 根据权利要求1所述的方法,其中,策略的业务属性信息与策略类型具有第二对应关系;
    所述第二对应关系用于所述终端基于所述第一策略中的业务属性信息确定所述第一策略对应的策略类型和/或业务类型。
  11. 根据权利要求10所述的方法,其中,所述业务属性信息包括以下至少之一:单网络切片选择辅助信息S-NSSAI、数据网络名DNN、IP地址、MAC地址、应用标识、会话类型。
  12. 根据权利要求1至11中任一项所述的方法,其中,所述终端请求第一策略的触发条件包括以下至少之一:
    第一策略到期时间、第一策略有效时间、发起第一请求消息的时间、发起第一请求消息的时间周期、发起第一请求消息的位置信息。
  13. 根据权利要求1至12中任一项所述的方法,其中,所述方法还包括:
    所述终端向所述网络设备发送第一请求消息,所述第一请求消息包括第二信息,所述第二信息用于指示所述网络设备更新目标策略类型和/或目标业务类型对应的策略。
  14. 根据权利要求13所述的方法,其中,所述第二信息包括目标策略类型和/或目标业务类型对应的策略标识。
  15. 根据权利要求13所述的方法,其中,所述第二信息包括所述终端存储的策略标识和以下至少一种信息:目标策略类型、目标业务类型。
  16. 根据权利要求13所述的方法,其中,所述第二信息包括目标策略类型和/或目标业务类型。
  17. 根据权利要求1至16中任一项所述的方法,其中,所述网络设备为策略控制功能网元PCF,所述第一信息由PCF封装在容器中发送给核心接入和移动性管理网元AMF,所述容器通过所述AMF透传给所述终端。
  18. 根据权利要求17所述的方法,其中,所述容器通过所述AMF采用NAS消息发送给所述终端。
  19. 根据权利要求13至16中任一项所述的方法,其中,所述网络设备为PCF,所述第二信息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
  20. 根据权利要求19所述的方法,其中,所述容器通过所述终端采用NAS消息发送给所述AMF。
  21. 根据权利要求1至20中任一项所述的方法,其中,所述第一策略对应的策略类型包括以下至少之一:V2X策略、高可靠低时延URLLC策略、物联网IoT策略、WLAN选择策略、URSP策略、背景数据传输策略。
  22. 根据权利要求1至20中任一项所述的方法,其中,所述第一策略对应的业务类型包括以下至少之一:V2X业务、URLLC业务、IoT业务、背景数据传输业务。
  23. 一种策略确定方法,所述方法包括:
    终端向所述网络设备发送第一请求消息,所述第一请求消息包括第二信息,所述第二信息用于指示所述网络设备更新目标策略类型和/或目标业务类型对应的策略。
  24. 根据权利要求23所述的方法,其中,所述第二信息包括目标策略类型和/或目标业务类型对应的策略标识。
  25. 根据权利要求23所述的方法,其中,所述第二信息包括所述终端存储的策略标识和以下至少一种信息:目标策略类型、目标业务类型。
  26. 根据权利要求23所述的方法,其中,所述第二信息包括目标策略类型和/或目标业务类型。
  27. 根据权利要求23至26中任一项所述的方法,其中,所述网络设备为PCF,所述第二信息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
  28. 根据权利要求27所述的方法,其中,所述容器通过所述终端采用NAS消息发送给所述AMF。
  29. 一种策略确定装置,所述装置包括:
    接收单元,用于接收网络设备发送的第一信息,所述第一信息包括以下至少之一:第一策略、第一策略对应的策略类型、第一策略对应的业务类型、是否允许终端请求第一策略的指示信息、终端请求第一策略的触发条件。
  30. 根据权利要求29所述的装置,其中,所述第一策略中的策略内容中包括第一指示信息,所述第一指示信息用于指示所述第一策略对应的策略类型和/或业务类型。
  31. 根据权利要求30所述的装置,其中,所述第一策略中的策略内容中的策略 类型字段和/或备用比特位字段包括所述第一指示信息。
  32. 根据权利要求29所述的装置,其中,所述第一策略中的策略标识中包括第二指示信息,所述第二指示信息用于指示所述第一策略对应的策略类型和/或业务类型。
  33. 根据权利要求32所述的装置,其中,
    所述第一策略中的策略标识包括PLMN标识、第二指示信息和PSC;或者,
    所述第一策略中的策略标识包括PLMN标识和PSC,所述PSC包含所述第二指示信息。
  34. 根据权利要求29所述的装置,其中,策略标识的取值与策略类型具有第一对应关系;
    所述第一对应关系用于所述终端基于所述第一策略中的策略标识确定所述第一策略对应的策略类型和/或业务类型。
  35. 根据权利要求29所述的装置,其中,所述第一信息包括第一参数,所述第一参数用于指示第一策略与策略类型和/或业务类型的对应关系;
    所述第一参数用于所述终端确定所述第一策略对应的策略类型和/或业务类型。
  36. 根据权利要求35所述的装置,其中,所述第一策略与策略类型和/或业务类型的对应关系包括以下至少之一:
    至少一个策略标识与策略类型和/或业务类型之间的对应关系;
    至少一个策略规则与策略类型和/或业务类型之间的对应关系;
    至少一个策略分段与策略类型和/或业务类型之间的对应关系。
  37. 根据权利要求34至36中任一项所述的装置,其中,所述策略标识包括PLMN标识和PSC。
  38. 根据权利要求29所述的装置,其中,策略的业务属性信息与策略类型具有第二对应关系;
    所述第二对应关系用于所述终端基于所述第一策略中的业务属性信息确定所述第一策略对应的策略类型和/或业务类型。
  39. 根据权利要求38所述的装置,其中,所述业务属性信息包括以下至少之一:S-NSSAI、DNN、IP地址、MAC地址、应用标识、会话类型。
  40. 根据权利要求29至39中任一项所述的装置,其中,所述终端请求第一策略的触发条件包括以下至少之一:
    第一策略到期时间、第一策略有效时间、发起第一请求消息的时间、发起第一请求消息的时间周期、发起第一请求消息的位置信息。
  41. 根据权利要求29至40中任一项所述的装置,其中,所述装置还包括:
    发送单元,用于向所述网络设备发送第一请求消息,所述第一请求消息包括第二信息,所述第二信息用于指示所述网络设备更新目标策略类型和/或目标业务类型对应的策略。
  42. 根据权利要求41所述的装置,其中,所述第二信息包括目标策略类型和/或目标业务类型对应的策略标识。
  43. 根据权利要求41所述的装置,其中,所述第二信息包括所述终端存储的策略标识和以下至少一种信息:目标策略类型、目标业务类型。
  44. 根据权利要求41所述的装置,其中,所述第二信息包括目标策略类型和/或目标业务类型。
  45. 根据权利要求29至44中任一项所述的装置,其中,所述网络设备为PCF,所述第一信息由PCF封装在容器中发送给AMF,所述容器通过所述AMF透传给所 述终端。
  46. 根据权利要求45所述的装置,其中,所述容器通过所述AMF采用NAS消息发送给所述终端。
  47. 根据权利要求41至44中任一项所述的装置,其中,所述网络设备为PCF,所述第二信息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
  48. 根据权利要求47所述的装置,其中,所述容器通过所述终端采用NAS消息发送给所述AMF。
  49. 根据权利要求29至48中任一项所述的装置,其中,所述第一策略对应的策略类型包括以下至少之一:
    V2X策略、高可靠低时延URLLC策略、物联网CIoT策略、WLAN选择策略、URSP策略、背景数据传输策略。
  50. 根据权利要求29至48中任一项所述的装置,其中,所述第一策略对应的业务类型包括以下至少之一:V2X业务、URLLC业务、IoT业务、背景数据传输业务。
  51. 一种策略确定装置,所述装置包括:
    发送单元,用于向所述网络设备发送第一请求消息,所述第一请求消息包括第二信息,所述第二信息用于指示所述网络设备更新目标策略类型和/或目标业务类型对应的策略。
  52. 根据权利要求51所述的装置,其中,所述第二信息包括目标策略类型和/或目标业务类型对应的策略标识。
  53. 根据权利要求51所述的装置,其中,所述第二信息包括所述终端存储的策略标识和以下至少一种信息:目标策略类型、目标业务类型。
  54. 根据权利要求51所述的装置,其中,所述第二信息包括目标策略类型和/或目标业务类型。
  55. 根据权利要求51至54中任一项所述的装置,其中,所述网络设备为PCF,所述第二信息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
  56. 根据权利要求55所述的装置,其中,所述容器通过所述终端采用NAS消息发送给所述AMF。
  57. 一种终端,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求1至22中任一项所述的方法,或者权利要求23至28中任一项所述的方法。
  58. 一种芯片,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至22中任一项所述的方法,或者权利要求23至28中任一项所述的方法。
  59. 一种计算机可读存储介质,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求1至22中任一项所述的方法,或者权利要求23至28中任一项所述的方法。
  60. 一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至22中任一项所述的方法,或者权利要求23至28中任一项所述的方法。
  61. 一种计算机程序,所述计算机程序使得计算机执行如权利要求1至22中任一项所述的方法,或者权利要求23至28中任一项所述的方法。
PCT/CN2019/079141 2019-03-21 2019-03-21 一种策略确定方法及装置、终端 WO2020186529A1 (zh)

Priority Applications (13)

Application Number Priority Date Filing Date Title
AU2019435787A AU2019435787A1 (en) 2019-03-21 2019-03-21 Policy determining method and apparatus, and terminal
CN202010584970.6A CN111741479B (zh) 2019-03-21 2019-03-21 一种策略确定方法及装置、终端、芯片、计算机存储介质
BR112021009804-6A BR112021009804A2 (pt) 2019-03-21 2019-03-21 método para determinação de política e dispositivo para determinação de política
CA3117244A CA3117244C (en) 2019-03-21 2019-03-21 Policy determining method and apparatus, and terminal
PCT/CN2019/079141 WO2020186529A1 (zh) 2019-03-21 2019-03-21 一种策略确定方法及装置、终端
SG11202104142UA SG11202104142UA (en) 2019-03-21 2019-03-21 Method and device for policy determination, and ue
MX2021006369A MX2021006369A (es) 2019-03-21 2019-03-21 Metodo y dispositivo para la determinacion de politicas, y ue.
KR1020217011680A KR20210145121A (ko) 2019-03-21 2019-03-21 정책 결정 방법 및 장치, 단말기
JP2021521537A JP7301962B2 (ja) 2019-03-21 2019-03-21 ポリシー決定方法及び装置、端末
EP19919915.9A EP3846579B1 (en) 2019-03-21 2019-03-21 Policy determining method and apparatus, and terminal
CN201980005882.1A CN111989984A (zh) 2019-03-21 2019-03-21 一种策略确定方法及装置、终端
US17/037,551 US11153444B2 (en) 2019-03-21 2020-09-29 Method and device for policy determination, and storage medium
US17/364,421 US11516350B2 (en) 2019-03-21 2021-06-30 Method and device for policy determination, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/079141 WO2020186529A1 (zh) 2019-03-21 2019-03-21 一种策略确定方法及装置、终端

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/037,551 Continuation US11153444B2 (en) 2019-03-21 2020-09-29 Method and device for policy determination, and storage medium

Publications (1)

Publication Number Publication Date
WO2020186529A1 true WO2020186529A1 (zh) 2020-09-24

Family

ID=72519437

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/079141 WO2020186529A1 (zh) 2019-03-21 2019-03-21 一种策略确定方法及装置、终端

Country Status (11)

Country Link
US (2) US11153444B2 (zh)
EP (1) EP3846579B1 (zh)
JP (1) JP7301962B2 (zh)
KR (1) KR20210145121A (zh)
CN (1) CN111989984A (zh)
AU (1) AU2019435787A1 (zh)
BR (1) BR112021009804A2 (zh)
CA (1) CA3117244C (zh)
MX (1) MX2021006369A (zh)
SG (1) SG11202104142UA (zh)
WO (1) WO2020186529A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114449543A (zh) * 2020-10-30 2022-05-06 维沃移动通信有限公司 辅助信息获取方法、配置方法、终端和网络设备
WO2024104077A1 (zh) * 2022-11-15 2024-05-23 维沃移动通信有限公司 信息传输方法、装置、通信设备及可读存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112567774A (zh) * 2019-07-16 2021-03-26 Oppo广东移动通信有限公司 一种策略映射方法及装置、终端
WO2021026744A1 (zh) * 2019-08-12 2021-02-18 Oppo广东移动通信有限公司 一种策略配置方法、网络设备、终端设备
CN113993176B (zh) * 2021-09-26 2024-06-21 深圳市广和通无线股份有限公司 路由选择策略更新方法、终端及网络侧设备
CN114143292B (zh) * 2021-12-02 2023-12-22 中国联合网络通信集团有限公司 策略更新方法、装置及可读存储介质
CN116567841A (zh) * 2022-01-27 2023-08-08 维沃移动通信有限公司 策略处理方法、装置及网络功能
WO2024111772A1 (en) * 2022-11-23 2024-05-30 Samsung Electronics Co., Ltd. Systems and methods for ue policy update management

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109315004A (zh) * 2017-08-11 2019-02-05 华为技术有限公司 Pdu类型的设置方法、ue策略的设置方法及相关实体

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6286052B1 (en) * 1998-12-04 2001-09-04 Cisco Technology, Inc. Method and apparatus for identifying network data traffic flows and for applying quality of service treatments to the flows
US7165112B2 (en) 2001-06-22 2007-01-16 Motorola, Inc. Method and apparatus for transmitting data in a communication system
JP2004303190A (ja) * 2003-03-20 2004-10-28 Hitachi Ltd プログラム、情報処理装置、情報処理装置の制御方法、及び記録媒体
CN100499558C (zh) 2003-09-29 2009-06-10 中兴通讯股份有限公司 在atm适配层实现混合分片重组的方法
WO2010054354A2 (en) * 2008-11-10 2010-05-14 Research In Motion Limited Method and system for supporting sip session policy using existing authorization architecture and protocols
CN108235270B (zh) 2013-01-22 2021-03-02 华为技术有限公司 一种进行策略决策的方法、计费设备和系统
US10194303B2 (en) * 2014-03-14 2019-01-29 Qualcomm Incorporated Packet filter based access control
US10231250B2 (en) * 2017-03-20 2019-03-12 Qualcomm Incorporated Policy communication via control plane signaling
WO2018201506A1 (zh) * 2017-05-05 2018-11-08 华为技术有限公司 一种通信方法及相关装置
US10701587B2 (en) * 2017-10-15 2020-06-30 Qualcomm Incorporated Policy provisioning at a user equipment (UE)
KR102709496B1 (ko) * 2018-04-05 2024-09-26 삼성전자주식회사 무선 통신 시스템에서 사용자 장치의 정책 관리를 위한 장치 및 방법
US11432135B2 (en) * 2018-06-19 2022-08-30 Apple Inc. Vehicle-to-everything (V2X) control function based on user equipment (UE) capability
KR102456859B1 (ko) * 2018-10-05 2022-10-20 삼성전자 주식회사 5g 시스템에서 제공하는 서비스 파라미터를 단말과 네트워크에 프로비져닝하는 방법
US10609667B1 (en) * 2019-01-28 2020-03-31 Verizon Patent And Licensing Inc. System and method for delivery of end device policies during registration procedure
WO2020160178A1 (en) * 2019-01-29 2020-08-06 Apple Inc. V2x ue with different pc5 rat capability in 5gs

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109315004A (zh) * 2017-08-11 2019-02-05 华为技术有限公司 Pdu类型的设置方法、ue策略的设置方法及相关实体

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
INTEL; QUALCOMM INCORPORATED; LG ELECTRONICS; OPPO; SAMSUNG; HUAWEI; HISILICON: "UE Triggered UE Policy Provisioning Procedure", 3GPP DRAFT; S2-1901884, 1 March 2019 (2019-03-01), Santa Cruz - Tenerife, Spain, pages 1 - 3, XP051610463 *
OPPO; CHINA UNICOM: "Clarification on Using PSI", 3GPP DRAFT; S2-183203, 20 April 2018 (2018-04-20), Sanya, China, pages 1 - 5, XP051437575 *
See also references of EP3846579A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114449543A (zh) * 2020-10-30 2022-05-06 维沃移动通信有限公司 辅助信息获取方法、配置方法、终端和网络设备
WO2024104077A1 (zh) * 2022-11-15 2024-05-23 维沃移动通信有限公司 信息传输方法、装置、通信设备及可读存储介质

Also Published As

Publication number Publication date
JP7301962B2 (ja) 2023-07-03
KR20210145121A (ko) 2021-12-01
EP3846579A4 (en) 2021-09-22
CA3117244C (en) 2023-07-04
US20210329131A1 (en) 2021-10-21
BR112021009804A2 (pt) 2021-08-17
AU2019435787A1 (en) 2021-05-27
SG11202104142UA (en) 2021-05-28
CN111989984A (zh) 2020-11-24
US11153444B2 (en) 2021-10-19
US11516350B2 (en) 2022-11-29
US20210029253A1 (en) 2021-01-28
EP3846579B1 (en) 2022-12-21
CA3117244A1 (en) 2020-09-24
EP3846579A1 (en) 2021-07-07
JP2022530587A (ja) 2022-06-30
MX2021006369A (es) 2021-08-11

Similar Documents

Publication Publication Date Title
WO2020186529A1 (zh) 一种策略确定方法及装置、终端
US20210127317A1 (en) Path selecting method, terminal device, and network device
WO2020191683A1 (zh) 一种测量间隔配置方法及装置、终端、网络设备
CN111741479B (zh) 一种策略确定方法及装置、终端、芯片、计算机存储介质
CA3108685A1 (en) Information transmission method and apparatus, and communication device
WO2019242712A1 (zh) 一种能力交互方法及相关设备
WO2020206677A1 (zh) 一种配置策略的方法及装置、网络设备、终端
WO2021087828A1 (zh) 激活或者更新srs的路损rs的方法和设备
WO2020019910A1 (zh) 一种车联网中的通信方法及终端设备、网络设备
US20220124630A1 (en) Method and device for activating or updating pusch pathloss rs
US11864028B2 (en) Data transmission method, terminal device and core network device
WO2021120205A1 (zh) 无线通信的方法、终端设备和网络设备
WO2020199105A1 (zh) 数据绑定方法、信息更新方法及装置、终端
WO2020010619A1 (zh) 数据传输方法、终端设备和网络设备
WO2020223907A1 (zh) 一种信息传输方法及装置、网络设备
WO2020087546A1 (zh) 一种网络信息传输方法、获取方法、网络设备及终端设备
WO2020061851A1 (zh) 无线通信方法和基站
WO2020062042A1 (zh) 无线通信方法和设备
WO2020000174A1 (zh) 一种核心网选择方法及装置、终端设备、网络设备
WO2020042038A1 (zh) 通信方法和设备
US20210243833A1 (en) Radio communication method, terminal device and network device
WO2020164019A1 (zh) 一种承载配置方法及装置、网络设备
WO2020082327A1 (zh) 一种切换过程中的信令交互方法及装置、网络设备
WO2020061916A1 (zh) 一种触发状态的确定方法及装置、终端、网络设备
WO2020077645A1 (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: 19919915

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021521537

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 3117244

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2019919915

Country of ref document: EP

Effective date: 20210401

ENP Entry into the national phase

Ref document number: 2019435787

Country of ref document: AU

Date of ref document: 20190321

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112021009804

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 112021009804

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20210520

NENP Non-entry into the national phase

Ref country code: DE