WO2020206677A1 - 一种配置策略的方法及装置、网络设备、终端 - Google Patents

一种配置策略的方法及装置、网络设备、终端 Download PDF

Info

Publication number
WO2020206677A1
WO2020206677A1 PCT/CN2019/082432 CN2019082432W WO2020206677A1 WO 2020206677 A1 WO2020206677 A1 WO 2020206677A1 CN 2019082432 W CN2019082432 W CN 2019082432W WO 2020206677 A1 WO2020206677 A1 WO 2020206677A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
policy
parameter
rsd
message
Prior art date
Application number
PCT/CN2019/082432
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
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2019/082432 priority Critical patent/WO2020206677A1/zh
Priority to CN201980021636.5A priority patent/CN112088558B/zh
Publication of WO2020206677A1 publication Critical patent/WO2020206677A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/04Wireless resource allocation

Definitions

  • the embodiments of the present application relate to the field of mobile communication technology, and specifically relate to a method and device for configuring a policy, network equipment, and a terminal.
  • UE policy User Equipment policy
  • UE policy User Equipment policy
  • PSI Policy Section Identifier
  • the terminal After receiving the UE policy, the terminal will feed back to the network whether the UE policy is accepted by the terminal, that is, whether the UE policy is successfully configured.
  • the current mechanism only supports the terminal to feed back the policy configuration result to the network with the granularity of PSI, which causes the network to be unable to accurately determine which policies the terminal has successfully configured.
  • the embodiment of the application provides a method and device for configuring a policy, network equipment, and terminal.
  • the network device receives a first message sent by the terminal, where the first message is used to notify the network device of a policy configuration result corresponding to the first policy type.
  • the terminal receives the first policy sent by the network device, where when the terminal does not support the first part of the content in the first policy, the terminal uses the content other than the first part of the first policy.
  • the device provided by the embodiment of the application is applied to network equipment, and the device includes:
  • the receiving unit is configured to receive a first message sent by the terminal, where the first message is used to notify the network device of the policy configuration result corresponding to the first policy type.
  • the device provided in the embodiment of the present application is applied to a terminal, and the device includes:
  • the receiving unit is configured to receive a first policy sent by a network device, wherein when the terminal does not support the first part of the content in the first policy, the terminal uses the first policy except for the first part of the content Content.
  • the network device provided by 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 method of configuring a 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 method of configuring a strategy.
  • the chip provided in the embodiment of the present application is used to implement the above-mentioned configuration strategy 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 method of configuration strategy.
  • 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 method of configuring a policy.
  • the computer program product provided by the embodiment of the present application includes computer program instructions that cause a computer to execute the above-mentioned method of configuring a strategy.
  • the computer program provided by the embodiment of the present application when it runs on a computer, causes the computer to execute the above-mentioned method of configuring a policy.
  • the terminal feeds back the policy configuration result to the network device at the granularity of the policy type, so that the network device can determine which policy type of policy the terminal has successfully configured.
  • the network device can determine the type of policy supported by the terminal, thereby avoiding the network device from transmitting irrelevant or useless policies to the terminal, and achieving more efficient policy negotiation and transmission.
  • FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.
  • Figure 2 is a system architecture diagram of a 5G network according to an embodiment of the present application.
  • FIG. 3 is a configuration flowchart of UE policy provided by an embodiment of this application.
  • FIG. 4 is a flowchart of a UE actively requesting a UE policy according to an embodiment of this application;
  • Figure 5-1 is a schematic diagram of a UE policy segment management list information unit
  • Figure 5-2 is a schematic diagram of the content of the UE policy segment management list
  • Figure 5-3 is a schematic diagram of the UE policy segment management sublist
  • Figure 5-4 is a schematic diagram of the content of the UE policy segment management sublist
  • Figure 5-5 is a schematic diagram of instruction
  • Figure 5-6 is a schematic diagram of the content of UE policy segmentation
  • Figure 5-7 is a schematic diagram of the UE strategy part
  • FIG. 6-1 is a schematic diagram of UPSI list information unit
  • FIG 6-2 is a schematic diagram of the UPSI sublist
  • Figure 7-1 is a schematic diagram of the UE policy segment management result information unit
  • Figure 7-2 is a schematic diagram of the content of the UE policy segment management result
  • Figure 7-3 is a schematic diagram of the UE policy segment management sub-result
  • Figure 7-4 is a schematic diagram of the content of the UE policy segment management sub-result
  • Figure 7-5 is a schematic diagram of Result
  • FIG. 8 is a schematic flowchart of a method for configuring a policy provided by an embodiment of the present application.
  • FIG. 9 is a registration flowchart provided by an embodiment of the application.
  • FIG. 10 is a flowchart of UE policy configuration provided by an embodiment of the present application.
  • FIG. 11 is a flowchart of the policy type that the AF provides to the PCF supported by the UE according to an embodiment of the present application;
  • FIG. 12 is a schematic diagram 1 of the structural composition of an apparatus for configuring a strategy provided by an embodiment of the present application.
  • FIG. 13 is a schematic diagram 2 of the structural composition of a device for configuring a strategy provided by an embodiment of the present application;
  • FIG. 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a chip of an embodiment of the present application.
  • FIG. 16 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 public land mobile networks (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, hub
  • 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.
  • the access terminal can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a 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 associates the application (or application data stream) to the corresponding PDU session for transmission based on URSP.
  • the mechanism is as follows:
  • the UE uses the URSP rule in the URSP to check whether the characteristics of the application data match the Traffic Descriptor of a rule in the URSP rule.
  • the order of viewing is based on the priority in the Traffic Descriptor in the URSP rule ( Precedence) to determine, that is, the UE checks the matching situation in sequence based on the order of priority.
  • a URSP rule is matched, it uses the RSD list under the URSP rule to bind the PDU session.
  • the UE searches for a suitable PDU session according to the Precedence order in the RSD.
  • the RSD with higher priority is preferentially used here. If a parameter in the RSD has one or more values, the UE selects One of them is combined with other parameters to find whether the PDU session exists:
  • the UE If it does not exist, the UE triggers the establishment of the PDU session, and the UE reports the attribute parameters of the PDU session in the establishment request message; further,
  • the UE will bind the application data to the session for transmission;
  • the UE searches for the existence of the PDU session again based on other parameter combinations in the RSD or using the parameter combination in the RSD of the second priority (cycle step 1));
  • the UE searches for the Traffic Descriptor in the second-priority URSP rule according to the Precedence order to see if it can match the application data stream characteristics. When it matches, repeat The process described earlier.
  • LADN DNN availability The data network name (LADN DNN availability) is updated
  • -UE is registered to 3GPP access network or non-3GPP access network;
  • the UE establishes a connection to the WLAN access network.
  • 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.
  • FIG. 2 is a system architecture diagram of the 5G network according to an embodiment of the application. As shown in Figure 2, the equipment involved in the 5G network system includes:
  • UE User Equipment
  • RAN Radio Access Network
  • UPF User Plane Function
  • DN Data Network
  • AMF Access and Mobility Management Function
  • Session Management Function Session Management Function
  • PCF Policy Control Function
  • AF Application Function
  • AUSF Authentication Server Function
  • UDM Unified Data Management
  • the configuration of the UE policy is implemented through the UE Configuration Update (UCU) process.
  • UCU UE Configuration Update
  • the process includes the following steps:
  • Step 301 The PCF decides to update the UE policy.
  • Step 302 The PCF puts the UE policy to be updated in a container and sends it to the AMF.
  • Step 303 The AMF uses the NAS message to directly forward the container to the UE.
  • Step 304 The UE sends the policy configuration result (Result of the delivery of UE policies) to the AMF.
  • 3GPP stipulates the process for the UE to actively request the UE policy. As shown in Figure 4, the process includes the following steps:
  • Step 401 The UE sends a UE policy request message to the AMF.
  • Step 402 The AMF sends a UE policy control update message to the PCF.
  • Step 403 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. 3.
  • 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. 4 is only used for the request of the UE policy (that is, the V2X policy) of the V2X service.
  • the UE policy is transmitted in the following manner: the network device divides the UE policy into one or more policy segments and sends them to the terminal, where each policy segment corresponds to a 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 3).
  • the format of the UE policy is shown in Figure 5-1 to Figure 5-1.
  • Figure 5-1 is the UE policy section management list information element (UE policy section management list information element), including the length of the UE policy section management list content (Length of UE policy section management list contents) ) And the content of the UE policy section management list (UE policy section management list contents).
  • Figure 5-2 shows the content of the UE policy section management list (UE policy section management list contents), including N UE policy section management sublists (UE policy section management sublist).
  • Figure 5-3 shows the UE policy section management sublist (UE policy section management sublist), including the PLMN and UE policy section management sublist content (UE policy section management sublist contents), where the PLMN moves home Code (Mobile Country Code, MCC) and Mobile Network Code (Mobile Network Code, MNC) are composed.
  • PLMN Mobile Country Code
  • MNC Mobile Network Code
  • Figure 5-4 shows the contents of the UE policy section management sublist (UE policy section management sublist contents), including N instructions (Instruction).
  • Figure 5-5 is an instruction (Instruction), including instruction content length, UPSC, and UE policy section content (UE policy section content).
  • Figure 5-6 shows the UE policy section content, including N UE policy parts;
  • Figure 5-7 shows the UE policy part (UE policy part), including UE policies Partial content length (UE policy part contents length), spare (Spare) bits, UE policy part type (UE policy part type), UE policy part content (UE policy part contents).
  • PSI is also called UPSI
  • PSI itself is composed of PLMN ID and Policy Section Code (PSC).
  • PSC Policy Section Code
  • the terminal When the terminal performs the registration process or the process of actively applying for UE policy, it will carry its own stored PSI list (PSI list) in the Non-Access Stratum (NAS) message sent to the network, and the network side will also know Which strategies the terminal has stored, and update accordingly.
  • PSI list PSI list
  • NAS Non-Access Stratum
  • the format of the PSI list is shown in Figure 6-1 and Figure 6-2.
  • Figure 6-1 is the UPSI list information element, including the length of the PSI list (Length of UPSI list contents) and N items UPSI sublist (UPSI sublist); further, Figure 6-2 is the UPSI sublist (UPSI sublist), including the length of UPSI sublist (Length of UPSI sublist), PLMN and UPSC, where PLMN consists of MCC and MNC.
  • step 304 in Figure 3 above the UE will send the policy configuration result to the AMF.
  • the format of the policy configuration result is shown in Figure 7-1 to Figure 7-5, where Figure 7-1 shows the UE policy analysis.
  • Section management result information element (UE policy section management result information element), including the length of UE policy section management result content (Length of UE policy section management result contents) and UE policy section management result content (UE policy section management result) contents).
  • Figure 7-2 shows the content of UE policy section management results (UE policy section management result contents), including N UE policy section management subresults (UE policy section management subresult).
  • Figure 7-3 shows the UE policy section management subresult (UE policy section management subresult), including the content of the PLMN and UE policy section management subresult contents (UE policy section management subresult contents), where the PLMN consists of MCC and MNC composition.
  • Figure 7-4 shows the contents of the UE policy section management subresult contents (UE policy section management subresult contents), including N results (Result).
  • Figure 7-5 shows the result (Result), including UPSC, Failed instruction order and Cause.
  • the service types include at least one of the following: V2X service, URLLC service, IoT service, background data transmission service.
  • policies are defined as different policy types.
  • the policy types include at least one of the following: V2X policy, Ultra Reliable & Low Latency Communication (URLLC) policy, Internet of Things (Cognitive Internet of Things, CIoT) policy , WLAN selection strategy, URSP strategy, background data transmission strategy.
  • V2X policy Ultra Reliable & Low Latency Communication (URLLC) policy
  • URLLC Ultra Reliable & Low Latency Communication
  • CIoT Internet of Things
  • WLAN selection strategy Wireless Local Area Network
  • URSP strategy background data transmission strategy.
  • 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.
  • the type of business refers to the different business (business used) corresponding to different strategies.
  • the strategy used for the Internet of Vehicles corresponds to the V2X business
  • the strategy used for the Internet of Things corresponds to the Internet of Things business and is used for low-time
  • the high-reliability strategy corresponds to URLLC services, etc.
  • the UE policy can be mapped to different types of services.
  • FIG. 8 is a schematic flowchart of a method for configuring a policy provided by an embodiment of the application. As shown in FIG. 8, the method for configuring a policy includes the following steps:
  • Step 801 A network device receives a first message sent by a terminal, where the first message is used to notify the network device of a policy configuration result corresponding to the first policy type.
  • 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 message is a feedback message that the terminal replies to the network device after receiving the policy configured by the network device.
  • the purpose of the first message is to notify Network device policy configuration results.
  • the terminal may inform the network device of the policy configuration result based on the granularity of the policy type in the first message.
  • the terminal notifies the network device of the policy configuration result corresponding to the first policy type in the first message. For example: the terminal puts the "V2X policy unsuccessful" message in the first message and sends it to the network device.
  • the content of the first message may be implemented in at least one of the following ways:
  • the first message includes a first identifier and a policy configuration result corresponding to the first identifier, and the first identifier refers to an identifier of the first policy type.
  • a new identifier can be added to the Result, that is, an identifier used to indicate the first policy type. Since the result shown in Figure 7-5 is part of the UE policy section management subresult shown in Figure 7-3, it can be seen that a PLMN (composed of MCC and MNC)
  • One or more policy type identifiers can be associated with the following, that is to say, the policy configuration results of different policy types can be indicated within the granularity of PLMN.
  • the first message includes a second identifier and a policy configuration result corresponding to the second identifier, the second identifier refers to the identifier corresponding to the first policy segment, and the second identifier is identical to the first
  • the strategy type has a corresponding relationship.
  • the structure of the result (Result) in Figure 7-5 remains unchanged, and the result (Result) includes PSI.
  • the result (Result) includes PSI.
  • the second identifier in the first message has a corresponding relationship with the first policy type.
  • the network side can determine according to the second identifier (ie PSI) that the policy configuration result is the policy configuration result of the first policy type.
  • the first message includes a third identifier, and the third identifier is used to indicate that the configuration of a part of the content of the first policy is successful or unsuccessful.
  • a TD of a URP has both routing description (Route Selection Descriptors, RSD) and background data transmission (Background Data Transfer, BDT) strategies. If the terminal can only be configured with RSD, then the first message can be used to reply to the network device "BDT Partially not configured successfully" and/or "RSD partly configured successfully”.
  • RSD Route Selection Descriptors
  • BDT Background Data Transfer
  • the terminal receives the first policy sent by the network device, wherein, when the terminal does not support the first part of the first policy, the terminal uses the first policy except the first part Content other than content.
  • the first policy includes at least one rule, and each rule includes at least one RSD and at least one first parameter (that is, the first parameter is located outside the RSD), and the first A parameter is used to indicate a condition for using the session corresponding to the RSD, where, when the condition indicated by the first parameter is satisfied, the terminal can use the RSD to determine the binding relationship between the application and the session.
  • the first strategy may be URSP.
  • the rules in the first strategy refer to URSP rules.
  • all RSDs under the same URSP rule may be associated with one first parameter, or some RSDs under the same URSP rule may be associated with one first parameter.
  • the first parameters corresponding to one or more RSDs under the same URSP rule may be the same.
  • the first parameters corresponding to one or more RSDs under the same URSP rule may be different.
  • the first policy includes at least one rule, and each rule includes at least one RSD.
  • the RSD includes the first parameter, and the terminal uses the RSD
  • the parameters in determine the binding relationship between the application and the session that is, the terminal normally uses the RSD parameter to determine the binding relationship between the application and the session according to the evaluation behavior.
  • the terminal may 1) use the RSD ignoring the first parameter To determine the binding relationship between the application and the session, or 2) skip to the second rule of the second priority or the local configuration rule to continue to determine the binding relationship between the application and the session.
  • the first strategy may be URSP.
  • the rules in the first strategy refer to URSP rules.
  • all RSDs under the same URSP rule may include the first parameter, or some RSDs under the same URSP rule include the first parameter.
  • the first parameters corresponding to one or more RSDs under the same URSP rule may be the same.
  • the first parameters corresponding to one or more RSDs under the same URSP rule may be different.
  • the terminal may ignore the first parameter, and use the RSD other than the first parameter in the rule to determine the application and session That is, the terminal regards the content in the rule except the first parameter as a normal URSP rule.
  • the terminal when the terminal does not support the first parameter, the terminal may ignore the first parameter, and use the RSD that ignores the first parameter to determine the binding relationship between the application and the session.
  • the first parameter in the above solution of the present application includes the first time and/or the first location.
  • the network device is a PCF
  • the first message 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 above-mentioned solution of the embodiment of the present application is that the terminal notifies the network device of the policy configuration result corresponding to a specific policy type through the first message.
  • the embodiment of the present application may also include the following technical solutions, which can be combined with the above technical solutions It can also be implemented separately.
  • Solution 1 The network device sends a second message to the terminal, the second message includes at least one strategy segment, and each strategy segment includes a strategy corresponding to a strategy type. Further, the identifier of each strategy segment in the second message has a corresponding relationship with a strategy type.
  • each policy segment can only include a policy corresponding to one policy type.
  • the network device is a PCF
  • the second message is encapsulated in a container by the PCF and sent to the AMF
  • the container is transparently transmitted to the terminal through the AMF. Further, the container is sent to the terminal using a NAS message through the AMF.
  • Solution 2 The network device sends a second message to the terminal, where the second message includes at least one policy segment, and each of the policy segments includes a policy corresponding to at least one policy type supported by the terminal.
  • the network device since the terminal cannot configure the policy because some policy types are not supported, it can be specified that the network device only configures the policy corresponding to the policy type supported by the terminal.
  • the network device can learn the type of policy supported by the terminal in the following manner.
  • the network device determines the policy type supported by the terminal based on first information, and the first information comes from at least one of the following devices: terminal and AF.
  • the first information comes from the terminal.
  • the network device is a PCF
  • the policy type supported by the terminal is encapsulated in a container by the terminal and sent to the AMF, and the container is transparently transmitted to the PCF through the AMF. Further, the container is sent to the AMF by using a NAS message through the terminal.
  • the container is carried in a registration request message. In another embodiment, the container is carried in a terminal policy configuration request message.
  • the UE sends a registration request message to the AMF.
  • the registration request message carries a container, and the container encapsulates the policy type supported by the UE.
  • AMF interacts with PCF and delivers containers to PCF.
  • the AMF sends a registration request reply message to the UE, and the registration request reply message carries the policy types allowed/required by the UE to support.
  • the UE sends a UE policy configuration request message to the AMF.
  • the UE policy configuration request message carries a container, and the container encapsulates the policy type supported by the UE.
  • AMF passes the container to PCF.
  • the PCF sends the configured UE policy to the AMF.
  • the AMF sends a policy transmission message to the UE.
  • the policy transmission message carries the UE policy configured by the PCF and the policy type that the UE is allowed/required to support.
  • the first information comes from AF.
  • the network device is a PCF, and the policy type supported by the terminal is sent to the PCF by the AF.
  • the UE sends a UE policy configuration request message to the AF, and the application layer of the UE policy configuration request message carries the policy type supported by the UE. 2.
  • the AF informs the PCF of the policy type supported by the UE.
  • the network device is a PCF, and the policy type supported by the terminal is determined by the PCF according to the first information of the terminal. Further, the first information has a corresponding relationship with a policy type, and the first information includes at least one of the following: International Mobile Equipment Identity (IMEI), and subscription information corresponding to IMEI.
  • IMEI International Mobile Equipment Identity
  • subscription information corresponding to IMEI.
  • the IMEI is the device identification code of the terminal, and each terminal corresponds to an IMEI, so the capabilities of the terminal (for example, the type of policy supported by the terminal) can also be determined based on the IMEI.
  • the method further includes: the network device sends to the terminal the types of policies that are allowed to be supported by the terminal. Further, the policy type allowed by the terminal is sent to the terminal by the AMF using a NAS message.
  • FIG. 12 is a schematic diagram 1 of the structural composition of a device for configuring a policy according to an embodiment of the application.
  • the device for configuring a policy is applied to a network device.
  • the device for configuring a policy includes:
  • the receiving unit 1201 is configured to receive a first message sent by a terminal, where the first message is used to notify the network device of a policy configuration result corresponding to the first policy type.
  • the first message includes a first identifier and a policy configuration result corresponding to the first identifier, and the first identifier refers to an identifier of the first policy type.
  • the first message includes a second identifier and a policy configuration result corresponding to the second identifier
  • the second identifier refers to an identifier corresponding to the first policy segment
  • the second identifier corresponds to the
  • the first strategy type has a corresponding relationship.
  • the first message includes a third identifier, and the third identifier is used to indicate that the configuration of a part of the first policy is successful or unsuccessful.
  • the first policy includes at least one rule, and each rule includes at least one RSD.
  • the RSD includes a first parameter.
  • the terminal uses the parameters in the RSD to determine the binding between the application and the session. Definite relationship.
  • the terminal uses the RSD after ignoring the first parameter to determine the binding relationship between the application and the session, or the terminal uses the second rule of the second priority or the local configuration rule to determine the binding between the application and the session relationship.
  • the first policy includes at least one rule, and each rule includes at least one RSD and at least one first parameter.
  • the terminal can The RSD is used to determine the binding relationship between the application and the session.
  • the terminal when the terminal does not support the first parameter, the terminal ignores the first parameter.
  • the terminal when the terminal does not support the first parameter, the terminal uses the RSD that ignores the first parameter to determine the binding relationship between the application and the session; or, the terminal uses the rule to exclude The RSD other than the first parameter determines the binding relationship between the application and the session.
  • the network device is a PCF
  • the first message 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 device further includes:
  • the sending unit 1202 is configured to send a second message to the terminal, where the second message includes at least one strategy segment, and each strategy segment includes a strategy corresponding to a strategy type.
  • the identifier of each strategy segment in the second message has a corresponding relationship with a strategy type.
  • the device further includes:
  • the sending unit 1202 is configured to send a second message to the terminal, where the second message includes at least one strategy segment, and each strategy segment includes a strategy corresponding to at least one strategy type supported by the terminal.
  • the network device is a PCF
  • the second message 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 device further includes:
  • the determining unit 1203 is configured to determine the policy type supported by the terminal based on first information, where the first information comes from at least one of the following devices: terminal and AF.
  • the network device is a PCF
  • the policy type supported by the terminal is encapsulated in a container and sent to the AMF by the terminal, and 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 container is carried in a registration request message.
  • the container is carried in a terminal policy configuration request message.
  • the network device is a PCF
  • the policy type supported by the terminal is sent to the PCF by the AF.
  • the network device is a PCF
  • the policy type supported by the terminal is determined by the PCF according to the first information of the terminal.
  • the first information has a corresponding relationship with a policy type, and the first information includes at least one of the following: IMEI and subscription information corresponding to the IMEI.
  • the device further includes:
  • the sending unit 1202 is configured to send the policy types allowed by the terminal to the terminal.
  • the policy type allowed by the terminal is sent to the terminal by the AMF using a NAS message.
  • the first parameter includes a first time and/or a first location.
  • FIG. 13 is a schematic diagram 2 of the structural composition of a device for configuring a strategy provided by an embodiment of the application.
  • the device for configuring a strategy is applied to a terminal.
  • the device for configuring a strategy includes:
  • the receiving unit 1301 is configured to receive a first policy sent by a network device, wherein when the terminal does not support the first part of the content in the first policy, the terminal uses the first policy except the first part of the content Outside content.
  • the first policy includes at least one rule, and each rule includes at least one RSD.
  • the RSD includes a first parameter.
  • the terminal uses the parameters in the RSD to determine the binding between the application and the session. Definite relationship.
  • the terminal uses the RSD after ignoring the first parameter to determine the binding relationship between the application and the session, or the terminal uses the second rule of the second priority or the local configuration rule to determine the binding between the application and the session relationship.
  • the first policy includes at least one rule, and each rule includes at least one RSD and at least one first parameter.
  • the terminal can The RSD is used to determine the binding relationship between the application and the session.
  • the terminal when the terminal does not support the first parameter, the terminal ignores the first parameter.
  • the terminal when the terminal does not support the first parameter, the terminal uses the RSD that ignores the first parameter to determine the binding relationship between the application and the session; or, the terminal uses the rule to exclude The RSD other than the first parameter determines the binding relationship between the application and the session.
  • the first parameter includes a first time and/or a first location.
  • FIG. 14 is a schematic structural diagram of a communication device 600 according to an embodiment of the present application.
  • the communication device may be a network device, such as a PCF.
  • the communication device 600 shown in FIG. 14 includes a processor 610, and the processor 610 may call and run a computer program from the 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. 15 is a schematic structural diagram of a chip of an embodiment of the present application.
  • the chip 700 shown in FIG. 15 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 embodiment of the present application, and the chip can implement the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application.
  • the chip can implement the corresponding process implemented by the mobile terminal/terminal in each method of the embodiment of the present application.
  • it will not be omitted here. 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, etc.
  • FIG. 16 is a schematic block diagram of a communication system 900 according to an embodiment of the present application. As shown in FIG. 16, 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.
  • 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 above-mentioned 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 Field 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种配置策略的方法及装置、网络设备,包括:网络设备接收终端发送的第一消息,所述第一消息用于通知所述网络设备第一策略类型对应的策略配置结果。

Description

一种配置策略的方法及装置、网络设备、终端 技术领域
本申请实施例涉及移动通信技术领域,具体涉及一种配置策略的方法及装置、网络设备、终端。
背景技术
网络给终端下发用户设备策略(User Equipment policy,UE policy)时,将UE policy分为一个或多个策略分段(Policy Section)进行传输,其中,每一个策略分段对应一个标识,即策略分段标识(Policy Section Identifier,PSI)。终端接收UE policy后,会向网络反馈UE policy是否被终端接受,即UE policy是否配置成功。然而,目前的机制只支持终端以PSI的粒度向网络反馈策略配置结果,导致网络无法准确判断终端成功配置了哪些策略。
发明内容
本申请实施例提供一种配置策略的方法及装置、网络设备、终端。
本申请实施例提供的配置策略的方法,包括:
网络设备接收终端发送的第一消息,所述第一消息用于通知所述网络设备第一策略类型对应的策略配置结果。
本申请实施例提供的配置策略的方法,包括:
终端接收网络设备发送的第一策略,其中,所述终端不支持所述第一策略中的第一部分内容时,所述终端使用所述第一策略中除所述第一部分内容以外的内容。
本申请实施例提供的装置,应用于网络设备,所述装置包括:
接收单元,用于接收终端发送的第一消息,所述第一消息用于通知所述网络设备第一策略类型对应的策略配置结果。
本申请实施例提供的装置,应用于终端,所述装置包括:
接收单元,用于接收网络设备发送的第一策略,其中,所述终端不支持所述第一策略中的第一部分内容时,所述终端使用所述第一策略中除所述第一部分内容以外的内容。
本申请实施例提供的网络设备,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,执行上述的配置策略的方法。
本申请实施例提供的终端,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,执行上述的配置策略的方法。
本申请实施例提供的芯片,用于实现上述的配置策略的方法。
具体地,该芯片包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有该芯片的设备执行上述的配置策略的方法。
本申请实施例提供的计算机可读存储介质,用于存储计算机程序,该计算机程序使得计算机执行上述的配置策略的方法。
本申请实施例提供的计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行上述的配置策略的方法。
本申请实施例提供的计算机程序,当其在计算机上运行时,使得计算机执行上述的配置策略的方法。
通过上述技术方案,终端以策略类型为粒度向网络设备反馈策略配置结果,使得网络设备可以明确终端成功配置了哪种策略类型的策略。另一方面,网络设备可以确定出终端支持的策略类型,从而避免了网络设备向终端传递无关或无用的策略,达到更高效的策略协商和传输。
附图说明
此处所说明的附图用来提供对本申请的进一步理解,构成本申请的一部分,本申请的示意性实施例及其说明用于解释本申请,并不构成对本申请的不当限定。在附图中:
图1是本申请实施例提供的一种通信系统架构的示意性图;
图2是本申请实施例的5G网络的系统架构图;
图3是本申请实施例提供的UE policy的配置流程图;
图4是本申请实施例提供的UE主动请求UE policy的流程图;
图5-1是UE策略分段管理列表信息单元的示意图;
图5-2是UE策略分段管理列表的内容的示意图;
图5-3是UE策略分段管理子列表的示意图;
图5-4是UE策略分段管理子列表的内容的示意图;
图5-5是说明(Instruction)的示意图;
图5-6是UE策略分段内容的示意图;
图5-7是UE策略部分的示意图;
图6-1是UPSI列表信息单元的示意图;
图6-2是UPSI子列表的示意图;
图7-1是UE策略分段管理结果信息单元的示意图;
图7-2是UE策略分段管理结果的内容的示意图;
图7-3是UE策略分段管理子结果的示意图;
图7-4是UE策略分段管理子结果的内容的示意图;
图7-5是结果(Result)的示意图;
图8是本申请实施例提供的配置策略的方法的流程示意图;
图9是本申请实施例提供的注册流程图;
图10是本申请实施例提供的UE策略配置流程图;
图11是本申请实施例提供的AF向PCF提供UE支持的策略类型的流程图;
图12是本申请实施例提供的配置策略的装置的结构组成示意图一;
图13是本申请实施例提供的配置策略的装置的结构组成示意图二;
图14是本申请实施例提供的一种通信设备示意性结构图;
图15是本申请实施例的芯片的示意性结构图;
图16是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
本申请实施例的技术方案可以应用于各种通信系统,例如:全球移动通讯(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 PCTCN2019082432-appb-000001
表1:URSP Rule
Figure PCTCN2019082432-appb-000002
表2:RSD
URSP的使用方法如下:UE基于URSP将应用(或者说应用数据流)关联到相应的PDU会话上进行传输,机制如下:
当应用层出现数据时,UE使用URSP中的URSP规则来查看该应用数据的特征是否匹配到了URSP规则中的某一个规则的Traffic Descriptor上,查看的顺序按照URSP规则中Traffic Descriptor中的优先级(Precedence)来决定,即UE基于优先级的顺序依次查看匹配情况,当匹配到一个URSP规则时,就是用该URSP规则下的RSD列表进行PDU会话的绑定。
当有URSP规则匹配上时,UE按照RSD中的Precedence顺序来查找合适的PDU会话,这里优先使用优先级高的RSD,如果该RSD中的某个参数为一个或多个取值,则UE选用其中一个与其他参数一起组合查找PDU会话是否存在:
1)若存在,则将该应用数据绑定到该会话进行传输;
2)若不存在,则UE触发该PDU会话的建立,建立请求消息中UE上报PDU会话的属性参数;进一步,
2.1)若该会话建立成功,则UE将该应用数据绑定到该会话进行传输;
2.2)若该会话建立不成功,则UE基于该RSD中的其他参数组合或者使用次优先级的RSD中的参数组合再次查找PDU会话是否存在(循环步骤1));
若根据该匹配的URSP规则中都不能找到一个合适的PDU会话进行绑定,则UE根据Precedence顺序查找次优先的URSP规则中的Traffic Descriptor是否能够匹配该应用数据流特征,当匹配上时,重复之前描述的过程。
上述为应用寻找合适的PDU会话的过程本申请称之为“评估(evaluation)”,当寻找到合适的PDU会话绑定后,UE会在下面的情况下重新执行evaluation以确定原应用数据与PDU会话的绑定关系是否需要更新:
-PCF更新URSP;
-UE从EPC移动到5GC;
-Allowed NSSAI或者Configured NSSAI发生更新;
-有效的本地数据网络-数据网络名(LADN DNN availability)发生更新;
-UE注册到3GPP接入网或非3GPP接入网;
-UE建立到WLAN接入网的连接。
3)V2X策略
UE policy的类型除了包括URSP、WLANSP以外,还可以在用途上进行区分,比如有些UE policy用于eMBB业务,有些UE policy用于V2X业务。进一步,V2X策略分为PC5策略和Uu接口策略。
图2为本申请实施例的5G网络的系统架构图,如图2所示,5G网络系统中涉及到的设备包括:
终端(UE,User Equipment)、无线接入网(RAN,Radio Access Network)、用户平面功能(UPF,User Plane Function)、数据网络(DN,Data Network)、接入和移动性管理(AMF,Access and Mobility Management Function)、会话管理功能(SMF,Session Management Function)、策略控制功能(PCF,Policy Control Function)、应用功能(AF,Application Function)、鉴权服务器功能(AUSF,Authentication Server Function)、统一数据管理(UDM,Unified Data Management)。
UE policy的配置通过UE配置更新(UE Configuration Update,UCU)流程实现,UCU流程中的各个网元之间的连接架构可以参照图2。如图3所示,该流程包括以下步骤:
步骤301:PCF决定更新UE policy。
步骤302:PCF将要更新的UE policy放在一个容器(Container)里,发送给AMF。
步骤303:AMF使用NAS消息将容器直接转发给UE。
步骤304:UE向AMF发送策略配置结果(Result of the delivery of UE policies)。
3GPP规定了UE主动请求UE policy的流程,如图4所示,该流程包括以下步骤:
步骤401:UE向AMF发送UE policy请求消息。
步骤402:AMF向PCF发送UE policy控制更新消息。
步骤403:UE与PCF之间进行UE policy的配置流程。
这里,UE policy的配置流程参照图3所示的流程。
需要说明的是,UE可以同时从网络侧接收URSP、V2X策略等多种类型的UE policy。另一方面。图4所示的UE主动请求UE policy的流程只用于V2X业务的UE policy(即V2X策略)的请求。
在上述图3和图4的流程中,UE policy通过以下方式传输:网络设备将UE policy分为一个或多个策略分段发送给终端,其中,每一个策略分段对应一个PSI。以下对UE policy内容的编制格式进行说明,UE policy内容的编制格式用于网络侧发送给终端UE policy时使用(见图3所示的流程),UE policy的编制格式如图5-1至图5-7所示,其中,图5-1为UE策略分段管理列表信息单元(UE policy section management list information element),包括UE策略分段管理列表内容的长度(Length of UE policy section management list contents)和UE策略分段管理列表的内容(UE policy section management list contents)。进一步,图5-2为UE策略分段管理列表的内容(UE policy section management list contents),包括N个UE策略分段管理子列表(UE policy section management sublist)。进一步,图5-3为UE策略分段管理子列表(UE policy section management sublist),包括PLMN和UE策略分段管理子列表的内容(UE policy section management sublist contents),其中,PLMN由移动回家码(Mobile Country Code,MCC)和移动网络码(Mobile Network Code,MNC)组成。进一步,图5-4为UE策略分段管理子列表的内容(UE policy section management sublist contents),包括N个说明(Instruction)。进一步,图5-5为说明(Instruction),包括说明内容的长度(Instruction contents length)、UPSC和UE策略分段内容(UE policy section contents)。进一步,图5-6为UE策略分段内容(UE policy section contents),包括N个UE策略部分(UE policy part);进一步,图5-7为UE策略部分(UE policy part),包括UE策略部分内容的长度(UE policy part contents length)、备用(Spare)比特位、UE策略部分的类型(UE policy part type)、UE策略部分内容(UE policy part contents)。
上述方案中,PSI也叫UPSI,PSI本身由PLMN ID和策略分段码(Policy Section Code,PSC)组成。当终端执行注册流程或执行主动申请UE policy流程时,会在发给网络的非接入层(Non-Access Stratum,NAS)消息中携带自己存储的PSI列表(PSI list),网络侧也就知道该终 端已经存储了哪些策略,并据此进行更新。PSI list的编制格式如图6-1和图6-2所示,图6-1为UPSI列表信息单元(UPSI list information element),包括PSI list内容的长度(Length of UPSI list contents)和N个UPSI子列表(UPSI sublist);进一步,图6-2为UPSI子列表(UPSI sublist),包括UPSI子列表的长度(Length of UPSI sublist)、PLMN和UPSC,其中,PLMN由MCC和MNC组成。
另一方面,在上述图3中的步骤304中,UE会向AMF发送策略配置结果,策略配置结果的编制格式如图7-1至图7-5,其中,图7-1为UE策略分段管理结果信息单元(UE policy section management result information element),包括UE策略分段管理结果内容的长度(Length of UE policy section management result contents)和UE策略分段管理结果的内容(UE policy section management result contents)。进一步,图7-2为UE策略分段管理结果的内容(UE policy section management result contents),包括N个UE策略分段管理子结果(UE policy section management subresult)。进一步,图7-3为UE策略分段管理子结果(UE policy section management subresult),包括PLMN和UE策略分段管理子结果的内容(UE policy section management subresult contents),其中,PLMN由MCC和MNC组成。进一步,图7-4为UE策略分段管理子结果的内容(UE policy section management subresult contents),包括N个结果(Result)。进一步,图7-5为结果(Result),包括UPSC、失败说明命令(Failed instruction order)和原因(Cause)。
从上述策略配置结果的编制格式可以看到,UE回复UE policy是否配置成功的粒度是PSI粒度的。当下面的情况发生时会造成一定的问题:
假设PCF将业务1和业务2对应的策略全都放进一个Policy Section中(即对应一个PSI)下发给UE,但UE只支持业务1对应的策略的配置,那么UE会向网络侧回复该PSI配置失败,UE无法告知PCF只有业务1对应的策略配置成功而业务2对应的策略配置不成功。为此,提出了本申请实施例的以下技术方案,需要说明的是,上述与本申请相关的技术方案可以与以下本申请实施例的技术方案进行任意结合来实施。
本申请实施例的技术方案中,有两种方法来区分不同的策略:
1)按照业务类型来区分
具体地,不同的业务类型对应的策略,业务类型包括以下至少之一:V2X业务、URLLC业务、IoT业务、背景数据传输业务。
2)按照策略类型来区分
具体地,不同的策略定义成不同的策略类型,策略类型包括以下至少之一:V2X策略、高可靠低时延(Ultra Reliable&Low Latency Communication,URLLC)策略、物联网(Cognitive Internet of Things,CIoT)策略、WLAN选择策略、URSP策略、背景数据传输策略。
需要说明的是,策略类型可以是策略的名称不同,比如用于会话绑定的策略叫URSP策略、用于WLAN接入点选择的策略叫WLAN选择策略、用于车联网的策略叫V2X策略等。业务类型是指不同的策略部分对应的业务(被用于的业务)不同,比如用于车联网的那部分策略对应于V2X业务、用于物联网的策略对应于物联网业务、用于低时延高可靠的策略对应于URLLC业务等,可以将UE policy对应到不同类型的业务。
以下本申请实施例中都使用策略类型来描述,应理解,业务类型的描述同样适用于本申请实施例的技术方案。
图8为本申请实施例提供的配置策略的方法的流程示意图,如图8所示,所述配置策略的方法包以下步骤:
步骤801:网络设备接收终端发送的第一消息,所述第一消息用于通知所述网络设备第一策略类型对应的策略配置结果。
本申请实施例中,所述终端可以是手机、平板电脑、笔记本、车载终端、可穿戴式设备等任意能够与网络进行通信的设备。
本申请实施例中,在UCU流程中,所述第一消息是终端接收网络设备配置的策略后向网络设备回复的反馈消息,参照图3中的步骤304,所述第一消息的目的是通知网络设备策略配置结果。这里,终端可以在所述第一消息中基于策略类型的粒度来告知网络设备策略配置结果。
具体地:终端在第一消息中通知网络设备第一策略类型对应的策略配置结果。举个例子:终端将“V2X策略不成功”信息放在第一消息中发送给网络设备。
本申请实施例中,所述第一消息的内容可以通过以下至少一种方式来实现:
方式一:所述第一消息包括第一标识和所述第一标识对应的策略配置结果,所述第一标识是 指所述第一策略类型的标识。
具体地,参照图7-5,可以在结果(Result)中添加新的标识,即用于指示所述第一策略类型的标识。由于图7-5所示的结果(Result)是图7-3所示的UE策略分段管理子结果(UE policy section management subresult)其中的部分内容,可见,一个PLMN(由MCC和MNC组成)下可以关联一个或多个策略类型的标识,也就是说可以在PLMN粒度内指示不同的策略类型的策略配置结果。
方式二:所述第一消息包括第二标识和所述第二标识对应的策略配置结果,所述第二标识是指第一策略分段对应的标识,所述第二标识与所述第一策略类型具有对应关系。
具体地,参照图7-5,按照图7-5的结果(Result)的结构维持不变,结果(Result)中包括PSI,这种情况下,需要保证一个PSI与一种策略类型具有对应关系。对于本申请实施例而言,所述第一消息中的第二标识与所述第一策略类型具有对应关系。这样,网络侧接收到第一消息后,可以根据第二标识(即PSI)确定出策略配置结果是第一策略类型的策略配置结果。
方式三:所述第一消息包括第三标识,所述第三标识用于指示第一策略的一部分内容配置成功或不成功。
这里,如果不同的策略内容绑定到同一个TD下面,有可能终端只能成功配置一部分,另一部分配置不成功。比如:一个URSP的TD下面同时有路由选择描述(Route Selection Descriptors,RSD)和背景数据传输(Background Data Transfer,BDT)策略,终端如果只能配置RSD,那么可以通过第一消息回复网络设备“BDT部分没有配置成功”和/或“RSD部分配置成功”。
本申请实施例中,终端接收网络设备发送的第一策略,其中,所述终端不支持所述第一策略中的第一部分内容时,所述终端使用所述第一策略中除所述第一部分内容以外的内容。
1)在本申的一种实施方式中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD和至少一个第一参数(即第一参数位于RSD以外),所述第一参数用于指示使用所述RSD对应的会话的条件,其中,当所述第一参数指示的条件满足时,所述终端能够使用所述RSD确定应用与会话的绑定关系。
这里,第一策略可以是URSP。第一策略中的规则是指URSP规则。本申请实施例中,同一个URSP规则下的全部RSD可以都关联一个第一参数,或者,同一个URSP规则下的部分RSD关联一个第一参数。
可选地,同一个URSP规则下的一个或多个RSD对应的第一参数可以相同。
可选地,同一个URSP规则下的一个或多个RSD对应的第一参数可以不同。
2)本申请的另一种实施方式中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD,参照如下表3,所述RSD包含第一参数,终端使用所述RSD中的参数确定应用与会话的绑定关系,即终端按照评估(evaluation)行为正常使用RSD参数来确定应用与会话的绑定关系。当终端使用第一规则(如URSP规则)中的RSD(即RSD中的一组参数)均不能完成确定应用与会话的绑定关系时,所述终端可以1)使用忽略第一参数后的RSD来确定应用与会话的绑定关系,或2)跳到次优先级的第二规则或本地配置规则继续确定所述应用与会话的绑定关系。
这里,第一策略可以是URSP。第一策略中的规则是指URSP规则。本申请实施例中,同一个URSP规则下的全部RSD可以都包含第一参数,或者,同一个URSP规则下的部分RSD包含第一参数。
可选地,同一个URSP规则下的一个或多个RSD对应的第一参数可以相同。
可选地,同一个URSP规则下的一个或多个RSD对应的第一参数可以不同。
对于上述1)的情况,当所述终端不支持所述第一参数时,所述终端可以忽略所述第一参数,而使用所述规则中除所述第一参数以外的RSD确定应用与会话的绑定关系,即终端将所述规则中除所述第一参数以外的内容看做是普通的URSP规则。
对于上述2)的情况,当所述终端不支持所述第一参数时,所述终端可以忽略所述第一参数,而使用忽略所述第一参数的RSD确定应用与会话的绑定关系。
在一实施方式中,本申请上述方案中的所述第一参数包括第一时间和/或第一地点。
Figure PCTCN2019082432-appb-000003
表3:RSD
本申请实施例中,所述网络设备为PCF,所述第一消息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。进一步,所述容器通过所述终端采用NAS消息发送给所述AMF。参照图3中的步骤304。
本申请实施例的上述方案是终端通过第一消息向网络设备通知特定策略类型对应的策略配置结果,除以以外,本申请实施例还可以包括以下技术方案,以下技术方案可以与上述技术方案 结合起来实施,也可以单独进行实施。
方案1:所述网络设备向所述终端发送第二消息,所述第二消息包括至少一个策略分段,每个所述策略分段包含一种策略类型对应的策略。进一步,所述第二消息中的每个策略分段的标识与一种策略类型具有对应关系。
这里,由于终端只能以PSI的粒度来回复策略配置结果,那么网络设备向终端发送第二消息(即策略配置信息)时,每一个策略分段只能包含一种策略类型对应的策略。
也就是说,在方案1中,规定了PSI和策略类型的对应关系,即在策略配置信息中一个PSI里只能包含一种策略类型的策略。
本申请实施例中,所述网络设备为PCF,所述第二消息由PCF封装在容器中发送给AMF,所述容器通过所述AMF透传给终端。进一步,所述容器通过所述AMF采用NAS消息发送给所述终端。
方案2:所述网络设备向所述终端发送第二消息,所述第二消息包括至少一个策略分段,每个所述策略分段包含所述终端支持的至少一种策略类型对应的策略。
这里,由于终端无法配置策略是由于有些策略类型不支持,因此,可以规定网络设备只配置终端支持的策略类型对应的策略。
对于上述方案2,网络设备可以通过以下方式获知终端支持的策略类型。
所述网络设备基于第一信息,确定所述终端支持的策略类型,所述第一信息来自以下至少一种设备:终端、AF。
1)所述第一信息来自终端。所述网络设备为PCF,所述终端支持的策略类型由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。进一步,所述容器通过所述终端采用NAS消息发送给所述AMF。
在一实施方式中,所述容器携带在注册请求消息中。在另一实施方式中,所述容器携带在终端策略配置请求消息中。
举个例子:参照图9,1、UE向AMF发送注册请求消息,该注册请求消息携带容器,所述容器中封装有UE支持的策略类型。2、AMF与PCF交互,向PCF传递容器。3、AMF向UE发送注册请求回复消息,该注册请求回复消息携带允许/要求UE支持的策略类型。
举个例子:参照图10,1、UE向AMF发送UE策略配置请求消息,该UE策略配置请求消息携带容器,所述容器中封装有UE支持的策略类型。2、AMF将容器传递给PCF。3、PCF将配置的UE策略发送给AMF。4、AMF向UE发送策略传输消息,该策略传输消息携带PCF配置的UE策略,以及允许/要求UE支持的策略类型。
需要注意的是,上述图9和图10两个流程中的下行NAS消息中携带UE允许/要求的策略类型与上行NAS消息中UE支持的策略类型之间没有必然关系。
2)所述第一信息来自AF。所述网络设备为PCF,所述终端支持的策略类型由AF发送给所述PCF。
举个例子:参照图11,1、UE向AF发送UE策略配置请求消息,该UE策略配置请求消息的应用层携带UE支持的策略类型。2、AF通知PCF该UE支持的策略类型。
3)所述网络设备为PCF,所述终端支持的策略类型由所述PCF根据所述终端的第一信息确定。进一步,所述第一信息与策略类型具有对应关系,所述第一信息包括以下至少之一:国际移动设备识别码(International Mobile Equipment Identity,IMEI)、IMEI对应的签约信息。这里,IMEI为所述终端的设备识别码,每一个终端都对应一个IMEI,那么该终端的能力(例如该终端支持的策略类型)也可以基于IMEI来确定。
可选地,在上述1)、2)、3)的基础上,所述方法还包括:所述网络设备将允许终端支持的策略类型发送给所述终端。进一步,所述允许终端支持的策略类型由AMF采用NAS消息发送给所述终端。
图12为本申请实施例提供的配置策略的装置的结构组成示意图一,该配置策略的装置应用于网络设备,如图12所示,所述配置策略的装置包括:
接收单元1201,用于接收终端发送的第一消息,所述第一消息用于通知所述网络设备第一策略类型对应的策略配置结果。
在一实施方式中,所述第一消息包括第一标识和所述第一标识对应的策略配置结果,所述第一标识是指所述第一策略类型的标识。
在一实施方式中,所述第一消息包括第二标识和所述第二标识对应的策略配置结果,所述第 二标识是指第一策略分段对应的标识,所述第二标识与所述第一策略类型具有对应关系。
在一实施方式中,所述第一消息包括第三标识,所述第三标识用于指示第一策略的一部分内容配置成功或不成功。
在一实施方式中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD,所述RSD包含第一参数,所述终端使用所述RSD中的参数确定应用与会话的绑定关系。
在一实施方式中,所述终端使用忽略第一参数后的RSD确定应用与会话的绑定关系,或者,所述终端使用次优先级的第二规则或本地配置规则确定应用与会话的绑定关系。
在一实施方式中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD和至少一个第一参数,其中,当所述第一参数指示的条件满足时,所述终端能够使用所述RSD确定应用与会话的绑定关系。
在一实施方式中,所述终端不支持所述第一参数时,所述终端忽略所述第一参数。
在一实施方式中,所述终端不支持所述第一参数时,所述终端使用忽略所述第一参数的RSD确定应用与会话的绑定关系;或者,所述终端使用所述规则中除所述第一参数以外的RSD确定应用与会话的绑定关系。
在一实施方式中,所述网络设备为PCF,所述第一消息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
在一实施方式中,所述容器通过所述终端采用NAS消息发送给所述AMF。
在一实施方式中,所述装置还包括:
发送单元1202,用于向所述终端发送第二消息,所述第二消息包括至少一个策略分段,每个所述策略分段包含一种策略类型对应的策略。
在一实施方式中,所述第二消息中的每个策略分段的标识与一种策略类型具有对应关系。
在一实施方式中,所述装置还包括:
发送单元1202,用于向所述终端发送第二消息,所述第二消息包括至少一个策略分段,每个所述策略分段包含所述终端支持的至少一种策略类型对应的策略。
在一实施方式中,所述网络设备为PCF,所述第二消息由PCF封装在容器中发送给AMF,所述容器通过所述AMF透传给终端。
在一实施方式中,所述容器通过所述AMF采用NAS消息发送给所述终端。
在一实施方式中,所述装置还包括:
确定单元1203,用于基于第一信息,确定所述终端支持的策略类型,所述第一信息来自以下至少一种设备:终端、AF。
在一实施方式中,所述网络设备为PCF,所述终端支持的策略类型由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
在一实施方式中,所述容器通过所述终端采用NAS消息发送给所述AMF。
在一实施方式中,所述容器携带在注册请求消息中。
在一实施方式中,所述容器携带在终端策略配置请求消息中。
在一实施方式中,所述网络设备为PCF,所述终端支持的策略类型由AF发送给所述PCF。
在一实施方式中,所述网络设备为PCF,所述终端支持的策略类型由所述PCF根据所述终端的第一信息确定。
在一实施方式中,所述第一信息与策略类型具有对应关系,所述第一信息包括以下至少之一:IMEI、IMEI对应的签约信息。
在一实施方式中,所述装置还包括:
发送单元1202,用于将允许终端支持的策略类型发送给所述终端。
在一实施方式中,所述允许终端支持的策略类型由AMF采用NAS消息发送给所述终端。
在一实施方式中,所述第一参数包括第一时间和/或第一地点。
本领域技术人员应当理解,本申请实施例的上述配置策略的装置的相关描述可以参照本申请实施例的配置策略的方法的相关描述进行理解。
图13为本申请实施例提供的配置策略的装置的结构组成示意图二,该配置策略的装置应用于终端,如图13所示,所述配置策略的装置包括:
接收单元1301,用于接收网络设备发送的第一策略,其中,所述终端不支持所述第一策略中的第一部分内容时,所述终端使用所述第一策略中除所述第一部分内容以外的内容。
在一实施方式中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD,所述 RSD包含第一参数,所述终端使用所述RSD中的参数确定应用与会话的绑定关系。
在一实施方式中,所述终端使用忽略第一参数后的RSD确定应用与会话的绑定关系,或者,所述终端使用次优先级的第二规则或本地配置规则确定应用与会话的绑定关系。
在一实施方式中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD和至少一个第一参数,其中,当所述第一参数指示的条件满足时,所述终端能够使用所述RSD确定应用与会话的绑定关系。
在一实施方式中,所述终端不支持所述第一参数时,所述终端忽略所述第一参数。
在一实施方式中,所述终端不支持所述第一参数时,所述终端使用忽略所述第一参数的RSD确定应用与会话的绑定关系;或者,所述终端使用所述规则中除所述第一参数以外的RSD确定应用与会话的绑定关系。
在一实施方式中,所述第一参数包括第一时间和/或第一地点。
本领域技术人员应当理解,本申请实施例的上述配置策略的装置的相关描述可以参照本申请实施例的配置策略的方法的相关描述进行理解。
图14是本申请实施例提供的一种通信设备600示意性结构图。该通信设备可以是网络设备,如PCF,图14所示的通信设备600包括处理器610,处理器610可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图14所示,通信设备600还可以包括存储器620。其中,处理器610可以从存储器620中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器620可以是独立于处理器610的一个单独的器件,也可以集成在处理器610中。
可选地,如图14所示,通信设备600还可以包括收发器630,处理器610可以控制该收发器630与其他设备进行通信,具体地,可以向其他设备发送信息或数据,或接收其他设备发送的信息或数据。
其中,收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线,天线的数量可以为一个或多个。
可选地,该通信设备600具体可为本申请实施例的网络设备,并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该通信设备600具体可为本申请实施例的移动终端/终端,并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程,为了简洁,在此不再赘述。
图15是本申请实施例的芯片的示意性结构图。图15所示的芯片700包括处理器710,处理器710可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图15所示,芯片700还可以包括存储器720。其中,处理器710可以从存储器720中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器720可以是独立于处理器710的一个单独的器件,也可以集成在处理器710中。
可选地,该芯片700还可以包括输入接口730。其中,处理器710可以控制该输入接口730与其他设备或芯片进行通信,具体地,可以获取其他设备或芯片发送的信息或数据。
可选地,该芯片700还可以包括输出接口740。其中,处理器710可以控制该输出接口740与其他设备或芯片进行通信,具体地,可以向其他设备或芯片输出信息或数据。
可选地,该芯片可应用于本申请实施例中的网络设备,并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该芯片可应用于本申请实施例中的移动终端/终端,并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端实现的相应流程,为了简洁,在此不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
图16是本申请实施例提供的一种通信系统900的示意性框图。如图16所示,该通信系统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 (74)

  1. 一种配置策略的方法,所述方法包括:
    网络设备接收终端发送的第一消息,所述第一消息用于通知所述网络设备第一策略类型对应的策略配置结果。
  2. 根据权利要求1所述的方法,其中,所述第一消息包括第一标识和所述第一标识对应的策略配置结果,所述第一标识是指所述第一策略类型的标识。
  3. 根据权利要求1所述的方法,其中,所述第一消息包括第二标识和所述第二标识对应的策略配置结果,所述第二标识是指第一策略分段对应的标识,所述第二标识与所述第一策略类型具有对应关系。
  4. 根据权利要求1所述的方法,其中,所述第一消息包括第三标识,所述第三标识用于指示第一策略的一部分内容配置成功或不成功。
  5. 根据权利要求4所述的方法,其中,所述第一策略包括至少一个规则,每个所述规则包括至少一个路由选择描述RSD,所述RSD包含第一参数,所述终端使用所述RSD中的参数确定应用与会话的绑定关系。
  6. 根据权利要求5所述的方法,其中,所述终端使用忽略第一参数后的RSD确定应用与会话的绑定关系,或者,所述终端使用次优先级的第二规则或本地配置规则确定应用与会话的绑定关系。
  7. 根据权利要求4所述的方法,其中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD和至少一个第一参数,其中,当所述第一参数指示的条件满足时,所述终端能够使用所述RSD确定应用与会话的绑定关系。
  8. 根据权利要求5至7中任一项所述的方法,其中,所述终端不支持所述第一参数时,所述终端忽略所述第一参数。
  9. 根据权利要求5至8中任一项所述的方法,其中,所述终端不支持所述第一参数时,所述终端使用忽略所述第一参数的RSD确定应用与会话的绑定关系;或者,所述终端使用所述规则中除所述第一参数以外的RSD确定应用与会话的绑定关系。
  10. 根据权利要求1至9中任一项所述的方法,其中,所述网络设备为策略控制功能网元PCF,所述第一消息由终端封装在容器中发送给接入和移动性管理网元AMF,所述容器通过所述AMF透传给PCF。
  11. 根据权利要求10所述的方法,其中,所述容器通过所述终端采用NAS消息发送给所述AMF。
  12. 根据权利要求1至11中任一项所述的方法,其中,所述方法还包括:
    所述网络设备向所述终端发送第二消息,所述第二消息包括至少一个策略分段,每个所述策略分段包含一种策略类型对应的策略。
  13. 根据权利要求12所述的方法,其中,所述第二消息中的每个策略分段的标识与一种策略类型具有对应关系。
  14. 根据权利要求1至11中任一项所述的方法,其中,所述方法还包括:
    所述网络设备向所述终端发送第二消息,所述第二消息包括至少一个策略分段,每个所述策略分段包含所述终端支持的至少一种策略类型对应的策略。
  15. 根据权利要求12至14中任一项所述的方法,其中,所述网络设备为PCF,所述第二消息由PCF封装在容器中发送给AMF,所述容器通过所述AMF透传给终端。
  16. 根据权利要求15所述的方法,其中,所述容器通过所述AMF采用非接入层NAS消息发送给所述终端。
  17. 根据权利要求1至16中任一项所述的方法,其中,所述方法还包括:
    所述网络设备基于第一信息,确定所述终端支持的策略类型,所述第一信息来自以下至少一种设备:终端、AF。
  18. 根据权利要求17所述的方法,其中,所述网络设备为PCF,所述终端支持的策略类型由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
  19. 根据权利要求18所述的方法,其中,所述容器通过所述终端采用NAS消息发送给所述 AMF。
  20. 根据权利要求18或19所述的方法,其中,所述容器携带在注册请求消息中。
  21. 根据权利要求18或19所述的方法,其中,所述容器携带在终端策略配置请求消息中。
  22. 根据权利要求17所述的方法,其中,所述网络设备为PCF,所述终端支持的策略类型由AF发送给所述PCF。
  23. 根据权利要求17所述的方法,其中,所述网络设备为PCF,所述终端支持的策略类型由所述PCF根据所述终端的第一信息确定。
  24. 根据权利要求23所述的方法,其中,所述第一信息与策略类型具有对应关系,所述第一信息包括以下至少之一:国际移动设备识别码IMEI、IMEI对应的签约信息。
  25. 根据权利要求1至24中任一项所述的方法,其中,所述方法还包括:
    所述网络设备将允许终端支持的策略类型发送给所述终端。
  26. 根据权利要求25所述的方法,其中,所述允许终端支持的策略类型由AMF采用NAS消息发送给所述终端。
  27. 一种配置策略的方法,所述方法包括:
    终端接收网络设备发送的第一策略,其中,所述终端不支持所述第一策略中的第一部分内容时,所述终端使用所述第一策略中除所述第一部分内容以外的内容。
  28. 根据权利要求27所述的方法,其中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD,所述RSD包含第一参数,所述终端使用所述RSD中的参数确定应用与会话的绑定关系。
  29. 根据权利要求28所述的方法,其中,所述终端使用忽略第一参数后的RSD确定应用与会话的绑定关系,或者,所述终端使用次优先级的第二规则或本地配置规则确定应用与会话的绑定关系。
  30. 根据权利要求27所述的方法,其中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD和至少一个第一参数,其中,当所述第一参数指示的条件满足时,所述终端能够使用所述RSD确定应用与会话的绑定关系。
  31. 根据权利要求28至30中任一项所述的方法,其中,所述方法还包括:
    所述终端不支持所述第一参数时,所述终端忽略所述第一参数。
  32. 根据权利要求28至31中任一项所述的方法,其中,所述方法还包括:
    所述终端不支持所述第一参数时,所述终端使用忽略所述第一参数后的RSD确定应用与会话的绑定关系;或者,所述终端使用所述规则中除所述第一参数以外的RSD确定应用与会话的绑定关系。
  33. 一种配置策略的装置,应用于网络设备,所述装置包括:
    接收单元,用于接收终端发送的第一消息,所述第一消息用于通知所述网络设备第一策略类型对应的策略配置结果。
  34. 根据权利要求33所述的装置,其中,所述第一消息包括第一标识和所述第一标识对应的策略配置结果,所述第一标识是指所述第一策略类型的标识。
  35. 根据权利要求33所述的装置,其中,所述第一消息包括第二标识和所述第二标识对应的策略配置结果,所述第二标识是指第一策略分段对应的标识,所述第二标识与所述第一策略类型具有对应关系。
  36. 根据权利要求33所述的装置,其中,所述第一消息包括第三标识,所述第三标识用于指示第一策略的一部分内容配置成功或不成功。
  37. 根据权利要求36所述的装置,其中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD,所述RSD包含第一参数,所述终端使用所述RSD中的参数确定应用与会话的绑定关系。
  38. 根据权利要求37所述的装置,其中,所述终端使用忽略第一参数后的RSD确定应用与会话的绑定关系,或者,所述终端使用次优先级的第二规则或本地配置规则确定应用与会话的绑定关系。
  39. 根据权利要求36所述的装置,其中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD和至少一个第一参数,其中,当所述第一参数指示的条件满足时,所述终端能够使用所述RSD确定应用与会话的绑定关系。
  40. 根据权利要求37至39中任一项所述的装置,其中,所述终端不支持所述第一参数时, 所述终端忽略所述第一参数。
  41. 根据权利要求37至40中任一项所述的装置,其中,所述终端不支持所述第一参数时,所述终端使用忽略所述第一参数的RSD确定应用与会话的绑定关系;或者,所述终端使用所述规则中除所述第一参数以外的RSD确定应用与会话的绑定关系。
  42. 根据权利要求33至41中任一项所述的装置,其中,所述网络设备为PCF,所述第一消息由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
  43. 根据权利要求42所述的装置,其中,所述容器通过所述终端采用NAS消息发送给所述AMF。
  44. 根据权利要求33至43中任一项所述的装置,其中,所述装置还包括:
    发送单元,用于向所述终端发送第二消息,所述第二消息包括至少一个策略分段,每个所述策略分段包含一种策略类型对应的策略。
  45. 根据权利要求44所述的装置,其中,所述第二消息中的每个策略分段的标识与一种策略类型具有对应关系。
  46. 根据权利要求33至43中任一项所述的装置,其中,所述装置还包括:
    发送单元,用于向所述终端发送第二消息,所述第二消息包括至少一个策略分段,每个所述策略分段包含所述终端支持的至少一种策略类型对应的策略。
  47. 根据权利要求44至46中任一项所述的装置,其中,所述网络设备为PCF,所述第二消息由PCF封装在容器中发送给AMF,所述容器通过所述AMF透传给终端。
  48. 根据权利要求47所述的装置,其中,所述容器通过所述AMF采用NAS消息发送给所述终端。
  49. 根据权利要求33至48中任一项所述的装置,其中,所述装置还包括:
    确定单元,用于基于第一信息,确定所述终端支持的策略类型,所述第一信息来自以下至少一种设备:终端、AF。
  50. 根据权利要求49所述的装置,其中,所述网络设备为PCF,所述终端支持的策略类型由终端封装在容器中发送给AMF,所述容器通过所述AMF透传给PCF。
  51. 根据权利要求50所述的装置,其中,所述容器通过所述终端采用NAS消息发送给所述AMF。
  52. 根据权利要求50或51所述的装置,其中,所述容器携带在注册请求消息中。
  53. 根据权利要求50或51所述的装置,其中,所述容器携带在终端策略配置请求消息中。
  54. 根据权利要求49所述的装置,其中,所述网络设备为PCF,所述终端支持的策略类型由AF发送给所述PCF。
  55. 根据权利要求49所述的装置,其中,所述网络设备为PCF,所述终端支持的策略类型由所述PCF根据所述终端的第一信息确定。
  56. 根据权利要求55所述的装置,其中,所述第一信息与策略类型具有对应关系,所述第一信息包括以下至少之一:国际移动设备识别码IMEI、IMEI对应的签约信息。
  57. 根据权利要求33至56中任一项所述的装置,其中,所述装置还包括:
    发送单元,用于将允许终端支持的策略类型发送给所述终端。
  58. 根据权利要求57所述的装置,其中,所述允许终端支持的策略类型由AMF采用NAS消息发送给所述终端。
  59. 一种配置策略的装置,应用于终端,所述装置包括:
    接收单元,用于接收网络设备发送的第一策略,其中,所述终端不支持所述第一策略中的第一部分内容时,所述终端使用所述第一策略中除所述第一部分内容以外的内容。
  60. 根据权利要求59所述的装置,其中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD,所述RSD包含第一参数,所述终端使用所述RSD中的参数确定应用与会话的绑定关系。
  61. 根据权利要求60所述的装置,其中,所述终端使用忽略第一参数后的RSD确定应用与会话的绑定关系,或者,所述终端使用次优先级的第二规则或本地配置规则确定应用与会话的绑定关系。
  62. 根据权利要求59所述的装置,其中,所述第一策略包括至少一个规则,每个所述规则包括至少一个RSD和至少一个第一参数,其中,当所述第一参数指示的条件满足时,所述终端能够使用所述RSD确定应用与会话的绑定关系。
  63. 根据权利要求60至62中任一项所述的装置,其中,所述终端不支持所述第一参数时,所述终端忽略所述第一参数。
  64. 根据权利要求60至63中任一项所述的装置,其中,所述终端不支持所述第一参数时,所述终端使用忽略所述第一参数的RSD确定应用与会话的绑定关系;或者,所述终端使用所述规则中除所述第一参数以外的RSD确定应用与会话的绑定关系。
  65. 一种网络设备,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求1至26中任一项所述的方法。
  66. 一种终端,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求27至32中任一项所述的方法。
  67. 一种芯片,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至26中任一项所述的方法。
  68. 一种芯片,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求27至32中任一项所述的方法。
  69. 一种计算机可读存储介质,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求1至26中任一项所述的方法。
  70. 一种计算机可读存储介质,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求27至32中任一项所述的方法。
  71. 一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至26中任一项所述的方法。
  72. 一种计算机可读存储介质,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求27至32中任一项所述的方法。
  73. 一种计算机程序,所述计算机程序使得计算机执行如权利要求1至26中任一项所述的方法。
  74. 一种计算机程序,所述计算机程序使得计算机执行如权利要求27至32中任一项所述的方法。
PCT/CN2019/082432 2019-04-12 2019-04-12 一种配置策略的方法及装置、网络设备、终端 WO2020206677A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/082432 WO2020206677A1 (zh) 2019-04-12 2019-04-12 一种配置策略的方法及装置、网络设备、终端
CN201980021636.5A CN112088558B (zh) 2019-04-12 2019-04-12 一种配置策略的方法及装置、网络设备、终端

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/082432 WO2020206677A1 (zh) 2019-04-12 2019-04-12 一种配置策略的方法及装置、网络设备、终端

Publications (1)

Publication Number Publication Date
WO2020206677A1 true WO2020206677A1 (zh) 2020-10-15

Family

ID=72750805

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/082432 WO2020206677A1 (zh) 2019-04-12 2019-04-12 一种配置策略的方法及装置、网络设备、终端

Country Status (2)

Country Link
CN (1) CN112088558B (zh)
WO (1) WO2020206677A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113630390A (zh) * 2021-07-23 2021-11-09 谭静 基于大数据的终端设备的网络安全通信方法及装置
CN115086896A (zh) * 2021-03-12 2022-09-20 中国移动通信有限公司研究院 控制方法、装置、设备及可读存储介质
WO2023236639A1 (zh) * 2022-06-07 2023-12-14 中兴通讯股份有限公司 传输策略配置方法及其系统、存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023220998A1 (zh) * 2022-05-18 2023-11-23 Oppo广东移动通信有限公司 无线通信的方法、用户设备及网络设备

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101369909A (zh) * 2007-08-15 2009-02-18 华为技术有限公司 上报策略执行结果的方法、网络通信系统和设备
CN101990202A (zh) * 2009-07-29 2011-03-23 中兴通讯股份有限公司 更新用户策略的方法及应用服务器

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101369909A (zh) * 2007-08-15 2009-02-18 华为技术有限公司 上报策略执行结果的方法、网络通信系统和设备
CN101990202A (zh) * 2009-07-29 2011-03-23 中兴通讯股份有限公司 更新用户策略的方法及应用服务器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"3GPP TS24.501 V15.3.0", 3GPP TECHNICAL SPECIFICATION, 26 March 2019 (2019-03-26), DOI: 20191228165228A *

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115086896A (zh) * 2021-03-12 2022-09-20 中国移动通信有限公司研究院 控制方法、装置、设备及可读存储介质
CN113630390A (zh) * 2021-07-23 2021-11-09 谭静 基于大数据的终端设备的网络安全通信方法及装置
CN113630390B (zh) * 2021-07-23 2023-09-01 国网湖北省电力有限公司荆州供电公司 基于大数据的终端设备的网络安全通信方法及装置
WO2023236639A1 (zh) * 2022-06-07 2023-12-14 中兴通讯股份有限公司 传输策略配置方法及其系统、存储介质

Also Published As

Publication number Publication date
CN112088558A (zh) 2020-12-15
CN112088558B (zh) 2022-07-01

Similar Documents

Publication Publication Date Title
WO2021007785A1 (zh) 一种策略映射方法及装置、终端
WO2020014983A1 (zh) 会话管理方法、终端设备和网络设备
WO2020206677A1 (zh) 一种配置策略的方法及装置、网络设备、终端
WO2021217412A1 (zh) 一种确定终端策略行为的方法及装置、网络设备
JP7301962B2 (ja) ポリシー決定方法及び装置、端末
WO2020001099A1 (zh) 网络设备配置终端设备的方法、终端设备和网络设备
JP7401567B2 (ja) 無線通信の方法および装置
WO2020056611A1 (zh) 用于网络切片鉴权的方法和设备
WO2019242712A1 (zh) 一种能力交互方法及相关设备
WO2020015727A1 (zh) 路径选择的方法、终端设备和网络设备
WO2021030965A1 (zh) 一种中继选择方法及装置、终端设备
US20220124500A1 (en) Communication method, terminal device and network device
WO2020252793A1 (zh) 一种选择网络的方法、设备及存储介质
WO2021022460A1 (zh) 一种会话验证方法、电子设备及存储介质
US11706623B2 (en) Communication method in vehicle to everything, user equipment, and network device
WO2021022428A1 (zh) 无线通信的方法、终端设备和网络设备
WO2020000174A1 (zh) 一种核心网选择方法及装置、终端设备、网络设备
WO2020062042A1 (zh) 无线通信方法和设备
WO2020223907A1 (zh) 一种信息传输方法及装置、网络设备
WO2020010619A1 (zh) 数据传输方法、终端设备和网络设备
WO2020061851A1 (zh) 无线通信方法和基站
WO2022147836A1 (zh) 一种连接建立方法及装置、网络设备
WO2020199105A1 (zh) 数据绑定方法、信息更新方法及装置、终端
WO2020164019A1 (zh) 一种承载配置方法及装置、网络设备
WO2020103050A1 (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: 19924213

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19924213

Country of ref document: EP

Kind code of ref document: A1