WO2020134885A1 - 一种通信方法和网络设备 - Google Patents

一种通信方法和网络设备 Download PDF

Info

Publication number
WO2020134885A1
WO2020134885A1 PCT/CN2019/122414 CN2019122414W WO2020134885A1 WO 2020134885 A1 WO2020134885 A1 WO 2020134885A1 CN 2019122414 W CN2019122414 W CN 2019122414W WO 2020134885 A1 WO2020134885 A1 WO 2020134885A1
Authority
WO
WIPO (PCT)
Prior art keywords
service area
entity
service
function entity
network
Prior art date
Application number
PCT/CN2019/122414
Other languages
English (en)
French (fr)
Inventor
张云飞
Original Assignee
腾讯科技（深圳）有限公司
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 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to KR1020217008747A priority Critical patent/KR102480207B1/ko
Priority to EP19904490.0A priority patent/EP3905834B1/en
Priority to JP2021526259A priority patent/JP7162135B2/ja
Publication of WO2020134885A1 publication Critical patent/WO2020134885A1/zh
Priority to US17/204,301 priority patent/US11595797B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing 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/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing 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/06—Registration at serving network Location Register, VLR or user mobility server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to a communication method, a network function entity, a network device, and a computer-readable storage medium.
  • a service area identifier (service zone ID, service zone ID) is proposed as one of the metadata for discovering and selecting service producer instances.
  • the service area ID is used to identify the service area of the service producer instance.
  • the service framework support function (Service Framework Support Function, SFSF) supports the discovery of Network Function (NF) services based on the combination of service set ID (SET ID) and service area ID.
  • SET ID service set ID
  • the service area ID may be used to indicate that the target NF service instance should be selected from the service set in the specific service area identified by the service area ID.
  • the meaning of the service area ID can be one of the following two meanings:
  • the service area ID indicates the service area of the service producer instance
  • the service area ID indicates the area where the service producer instance is deployed.
  • the current communication protocol (TR23.742) only states that the consumer service instance can select the service producer instance based on the service area ID, but does not mention how the consumer service should specifically obtain the service producer instance service area ID. This limits the use of service area IDs in the service framework.
  • the embodiments of the present disclosure provide a communication method, a network function entity, a network device, and a computer-readable storage medium.
  • a communication method is disclosed.
  • the communication method is performed by a service area identity policy management entity of a core network.
  • the communication method includes:
  • Sending the information containing the service area identifier to the network function entity causes the network function entity to select a service producer instance from the service producers corresponding to the service area identifier.
  • a communication method is disclosed.
  • the communication method is performed by a network function entity of a core network.
  • the communication method includes:
  • a network function entity including:
  • the determination module is configured to: determine the service area identification
  • a sending module configured to send information containing the service area identifier to another network function entity, so that the other network function entity selects a service producer instance from the service producers corresponding to the service area identifier .
  • a network function entity including:
  • a receiving module which is configured to receive the information including the service area identifier sent by the service area identity policy management entity of the core network;
  • the processing module is configured to: obtain the service area identifier from the information, and select a service producer instance from the service producer corresponding to the service area identifier.
  • a network device which includes a processor and a memory, and the memory stores computer-readable instructions, which are implemented when the processor executes the The communication method described in the above embodiments of the present disclosure.
  • a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the communication method described in the above embodiments of the present disclosure is implemented.
  • the service area identification policy management entity of the core network determines the service area ID and sends information including the service area ID to other network function entities, so that the network function entity that receives the service area ID can use the Service area ID to select service producer instance.
  • FIG. 1 shows a schematic architecture diagram of an application environment of a communication method according to an exemplary embodiment of the present disclosure.
  • FIG. 2 shows a schematic flowchart of a communication method according to an exemplary embodiment of the present disclosure.
  • FIG. 3 shows a schematic flowchart of a communication method according to another exemplary embodiment of the present disclosure.
  • FIG. 4 shows a schematic diagram of sending and receiving a service area ID during UE registration according to an exemplary embodiment of the present disclosure.
  • FIG. 5 shows a schematic diagram of sending and receiving a service area ID during UE registration according to another exemplary embodiment of the present disclosure.
  • FIG. 6 shows a schematic diagram of sending and receiving a service area ID during UE registration according to yet another exemplary embodiment of the present disclosure.
  • FIG. 7 shows a schematic diagram of sending and receiving a service area ID during PDU session establishment according to an exemplary embodiment of the present disclosure.
  • FIG. 8 shows a schematic composition block diagram of a network function entity according to an exemplary embodiment of the present disclosure.
  • FIG. 9 shows a schematic composition block diagram of a network function entity according to another exemplary embodiment of the present disclosure.
  • FIG. 10 shows a schematic composition block diagram of a network device according to an exemplary embodiment of the present disclosure.
  • Fig. 1 is a schematic diagram illustrating an application environment of the communication method of the present disclosure according to an exemplary embodiment.
  • a terminal device (User Equipment, UE) 110 can communicate with a core network 130 through an access network such as a radio access network (Radio Access Network, RAN) 120.
  • the core network 130 may include one or more control plane network function (NF) entities and one or more user plane function UPF (User Plane Function) entities UPF1 137 and UPF2138.
  • the one or more control plane NF entities may be such as the service area identification policy management entity 131, the mobility management entity 132, the session management function (SMF) entity SMF 139 or other NF entities shown in FIG. NF1133, NF2134.
  • the core network 130 may communicate with one or more Application Function (AF) entities.
  • the AF entity can correspond to the self-operated business function of the operator or the business function provided by the third-party service provider, such as AF1135 and AF2136 shown in FIG.
  • the architecture shown in Figure 1 is a service-oriented architecture, and each consumer service can complete the communication process by using one or more service producers.
  • the service framework support function supports the use of the service area ID to indicate that the target NF service instance should be selected from the set of service producers in the specific service area identified by the service area ID.
  • the mobility management entity 132 may select one or more NF service instances from multiple other NF service instances (eg, multiple session management entity instances) based on the service area ID for use in the communication process.
  • the inventor of the present application proposes that the service area identification policy management entity 131 determines the service area ID and sends it to the network function entity (eg, mobility management entity 132, session management function entity SMF139 or other NF entities) so that the network function entity can use the service area ID to select the technical solution of the service producer instance.
  • the network function entity eg, mobility management entity 132, session management function entity SMF139 or other NF entities
  • the network function entity eg, mobility management entity 132, session management function entity SMF139 or other NF entities
  • the "service area identification policy management entity” described in this article does not specifically refer to a specific core network entity, but all the functions of the service area identification policy management (such as generating service area identification policies) in the core network.
  • NF entity collectively, for example, it may include but not limited to the core network policy control function (PCF, Policy Control Function) entity, unified data management (UDM, Unified Data Management) entity, service selection within the core network service framework Strategy management functions, etc.
  • PCF Policy Control Function
  • UDM Unified Data Management
  • the "mobility management entity” mentioned in this article does not specifically refer to a specific core network entity, but a general term for all NF entities with mobility management functions in the core network. For example, it can Including but not limited to access and mobility management function (AMF, Access and Mobility Management Function) entities, etc.
  • AMF Access and Mobility Management Function
  • the various core network functional entities described herein may be a network device or a combination of network devices having this function.
  • terminal device refers to any user equipment that can access the core network and communicate with other network devices or application servers, including mobile phones, tablet computers, notebook computers, and various smart home appliances.
  • FIG. 1 and the above description are only exemplary embodiments of the implementation environment involved in the communication method of the present disclosure, and it can be understood that there are various modifications to the implementation environment applicable to the embodiments of the present disclosure.
  • FIG. 2 shows a schematic flowchart of a communication method according to an exemplary embodiment of the present disclosure.
  • This example method may be performed by the service area identification policy management entity.
  • the embodiment of the communication method shown in FIG. 2 is a technical solution executed on the service area identification policy management entity side.
  • the example method includes steps S210-S220:
  • step S210 the service area identifier is determined.
  • the service area identification policy management entity may determine the service area ID in various ways. For example, the service area ID may be received from other core network entities, or the service area ID may be generated or selected based on known information.
  • the service area identification policy management entity determines the service area ID based on at least one of the following information: operator's policy; application function (AF) requirements (for example, the AF wishes to route user equipment to a certain Service area, the preference information of the service area can be sent to the network through the AF entity); local configuration data; management and operation and maintenance operation requirements (for example, service producers in a certain area need service upgrades, you can consider routing user equipment to In other service areas, to reduce the impact of service upgrades on user experience, wait until the upgrade is complete and then modify the service area ID to allow user equipment to be rerouted to the service producer with that service area ID).
  • AF application function
  • the service area identification policy management entity may determine and send the service area ID in real time based on one or more of the above-mentioned information, or may determine the service area ID in advance after obtaining the various information as described above and send it in real time or based on the request The determined service area ID.
  • the service area identification policy management entity may acquire at least one of the above items of information and determine the service area ID based on the acquired information.
  • the policy control function PCF entity determines the service area ID according to the configuration data and management and operation and maintenance operation requirements, so as to use the determined service area ID to determine the service producer instance for the relevant consumer service instance of the UE.
  • the unified data management UDM entity determines the service area ID according to the configuration data such as the subscription data of the UE to use it to determine the service producer instance for the relevant consumer service instance of the UE.
  • the function responsible for the service selection strategy in the service-based framework determines the service area ID of a service according to network management and operation and maintenance requirements, and uses it to determine the service producer instance for the UE under the service instance.
  • the AF entity may include the preferred service area ID or service area preference information in the request and send it to the Network Open Function (NEF, Network Exposure) Function entity,
  • NEF Network Exposure
  • the NEF entity decides whether to accept the request. If it is decided to accept the request, the NEF entity provides the preference information carried in the request to the service area identification policy management entity for use by the service area identification policy management entity in determining the service area ID.
  • the operator equipment or AF entity may directly send the preference information to the service area identification policy management entity.
  • determining the service area ID also includes determining the service type and/or time range to which the service area ID applies. That is, the service area ID is specified when which service types are selected.
  • Step S220 Send the information containing the service area identifier to the network function entity, so that the network function entity selects a service producer instance from the service producers corresponding to the service area identifier.
  • the network function entity in step S220 may refer to any core network entity that can select a service producer instance using the service area ID, for example, a mobility management entity, an SMF entity, or other network function entities.
  • the service area identification policy management entity may carry the service area ID determined in step S210 in other information and send it to another network function entity (such as a mobility management entity) in the communication process.
  • the first information including the service area ID may be sent to the network function entity during the registration process of the terminal device UE, or during the protocol data unit (PDU, Protocol, Data, Unit) session establishment (PDU) session of the terminal device, Send the second information including the service area ID to the network function entity.
  • PDU Protocol, Data, Unit
  • PDU protocol data unit
  • the service priority of the service area ID sent during the PDU session establishment process can be set higher than that sent during the UE registration process
  • the priority of using the service area ID of the service area that is, when the network function entity receives both the first information and the second information, the service area ID included in the second information is preferentially used
  • the service area ID sent during the PDU session establishment process is preferentially used.
  • the service area identification policy management entity may send at least one of the following in addition to the service area ID: the service type to which the service area ID applies; and the time range to which the service area ID applies. For example, information containing both the service area identifier and the service type to which the service area identifier applies may be sent. If the NF entity receives the service area ID and the specified service type to which it applies, it can use the service area ID for the specified service type. In some examples, if only the service area ID is received without the service type to which the service area ID applies, the service area ID may be used for all service types.
  • FIG. 3 shows a schematic flowchart of a communication method according to another exemplary embodiment of the present disclosure.
  • This example method may be performed by an NF entity (eg, mobility management entity, session management entity, or other NF entity) of the core network.
  • the embodiment of the communication method shown in FIG. 3 is a technical solution executed on the receiving entity side (for example, the mobility management entity side).
  • the example method includes steps S310 to S330:
  • Step S310 Receive information containing the service area identifier sent by the service area identifier policy management entity of the core network.
  • the NF entity may receive the information including the service area ID during the communication with the service area identification policy management entity. For example, during the registration process of the terminal device, receive the first information including the service area identification sent by the service area identification policy management entity; or receive the service area identification policy during the establishment of the protocol data unit session of the terminal device.
  • the level is set to be higher than the usage priority of the service area ID received during the UE registration process, that is, the service area ID received during the establishment of the PDU session is preferentially used.
  • Step S320 Obtain the service area identifier from the information.
  • the service area ID carried in it can be obtained by retrieving the relevant specified field in the information.
  • Step S330 Select a service producer instance from the service producers corresponding to the service area identifier.
  • the service consumer sends the service area ID to the SFSF when sending the service invocation request.
  • the SFSF supports selecting service producer instances from the service set of a specific service area based on the service area ID.
  • the network function entity can obtain the service area ID from the information, and select the service producer corresponding to the service area ID according to the service area ID. If the service area ID and the applicable specified service type are received, the network function entity may use the service area ID to select a service producer of the specified service type. If only the service area ID is received without the service type to which the service area ID applies, the service area ID can be used for the selection of service producers of all service types.
  • the network function entity includes a new network function entity and an old network function entity used before, so that switching between new and old NF entities serving the UE may occur, that is, switching from the old NF entity To the new NF entity.
  • the old NF entity may transmit the received and still valid service area ID (and specified service type) information to the new NF entity, and the new NF entity receives the service area ID from the old network function entity And continue to use.
  • the new NF entity receives the new service area ID information from the service area identification policy management entity
  • the use priority of the service area ID received from the old NF entity may be set lower than that from the service area identification policy management entity The use priority of the received service area ID.
  • the new NF entity overwrites the service area ID information received from the old NF entity with the new service area ID information received from the service area identification policy management entity.
  • the NF entity may transmit the received service area ID (and the specified service type and/or applicable time range) to other NF entities that are needed (eg, from AMF to SMF).
  • FIG. 4 shows a schematic diagram of sending and receiving a service area ID during UE registration according to an exemplary embodiment of the present disclosure.
  • the UE registration process includes an Access Management Policy Association (Access Management Policy) Establishment process.
  • the service area identification policy management entity may be a policy control function PCF entity, and the NF entity receiving the service area ID may be used as mobility An example of an AMF entity that manages an entity.
  • the PCF entity sends the information containing the determined service area ID to the AMF entity during the establishment of the access management policy association, and the AMF entity receives the information and obtains the service area ID from the information.
  • receiving the first information including the service area identifier sent by the service area identity policy management entity includes: the access and mobility management function entity in the access management strategy During the establishment of the association, the first information including the service area identifier sent by the policy control function entity is received.
  • FIG. 4 An example UE registration process is shown in FIG. 4, which only shows some steps related to UE registration, and omits some less related steps. As shown in FIG. 4, the UE registration process may include steps S41-S44:
  • step S41 the UE sends a registration request to the AMF.
  • step S42 the AMF selects the PCF.
  • Step S43 an access management (AM, Access Management) policy association establishment process is performed between the AMF and the PCF.
  • AMF Access Management
  • the disclosure does not limit the names of the processes and policies, as long as it is the service invocation type of the user's mobility management policy acquired from the PCF.
  • This process may be initiated by the AMF to the PCF. It can be understood that the process can also be initiated by other entities (for example, PCF), which is not limited in this disclosure.
  • PCF may include the determined service area ID (or also include the applicable service type and/or time range) in the interaction information with AMF and send it to AMF , AMF then receives the interaction information and obtains the service area ID from it.
  • the PCF may also send the specified service type and/or time range applicable to the service area ID to the AMF.
  • the information sent by PCF to AMF in this process includes:
  • Service type ServiceType 1, ServiceType 2
  • Service type ServiceType 3, ServiceType 4
  • the service area IDs 1 and 2 are included, and the service type of the service area ID 1 is specified as service types 1 and 2, and the service type of the service area ID 2 is service types 3 and 4.
  • AMF will select the service producer instance in the service area with service area ID 1 when selecting the service producer of service type 1 or service type 2, and then select service type 3 or service type 4 Of service producers, the service producer instance in the service zone with service zone ID 2 is selected.
  • AMF will select a service producer instance with any service area ID. This information example also applies to other embodiments described below.
  • step S44 the AMF sends a registration acceptance message to the UE.
  • FIG. 5 shows a schematic diagram of sending and receiving a service area ID during UE registration according to another exemplary embodiment of the present disclosure.
  • the UE registration process includes an access management policy update process
  • the service area identification policy management entity may be a policy control function PCF entity
  • the NF entity receiving the service area ID may be an AMF entity as an example of a mobility management entity.
  • the PCF entity sends the information containing the determined service area ID to the AMF entity during the access management policy update process, and the AMF entity receives the information and obtains the service area ID from the information.
  • receiving the first information including the service area identifier sent by the service area identity policy management entity includes: the access and mobility management function entity enters the access management strategy During the update process, the first information including the service area identifier sent by the policy control function entity is received.
  • FIG. 5 An example UE registration process is shown in FIG. 5, which shows only some steps related to UE registration, and omits some less related steps. As shown in FIG. 5, the UE registration process may include steps S51-S55:
  • step S51 the UE sends a registration request to the AMF.
  • step S52 the AMF selects the PCF.
  • step S53 the AMF sends a registration acceptance message to the UE.
  • Step S54 an access management policy update process is performed between the AMF and the PCF.
  • This process may be initiated by the AMF to the PCF. It can be understood that the process can also be initiated by other entities (for example, PCF), which is not limited in this disclosure.
  • This process can be performed after the UE policy association establishment (UE Policy Association) Establishment process, or it can be executed in parallel with the terminal equipment policy association establishment process.
  • UE Policy Association UE Policy Association
  • PCF may include the determined service area ID (or also include the applicable service type and/or time range) in the interaction information with AMF and send it to AMF , AMF then receives the interaction information and obtains the service area ID from it.
  • the PCF may also send the specified service type and/or time range applicable to the service area ID to the AMF.
  • Step S55 the registration is completed.
  • the service area IDs and applicable service types sent and received during the example UE registration process in Figures 4 and 5 above are all transactions for the UE before the de-attachment ( transaction) are valid.
  • the UE registration process includes a contract data acquisition process
  • the service area identification policy management entity may be a unified data management UDM entity
  • the NF entity that receives the service area ID may be an AMF entity that is an example of a mobility management entity.
  • the UDM entity sends the information containing the determined service area ID to the AMF entity during the contract data acquisition process, and the AMF entity receives the information and obtains the service area ID from it.
  • receiving the first information including the service area identifier sent by the service area identity policy management entity includes: the access and mobility management function entity in the contract data acquisition process Receiving the first information including the service area identifier sent by the unified data management entity.
  • FIG. 6 An example UE registration process is shown in FIG. 6, which only shows some steps related to UE registration, and omits some less related steps. As shown in FIG. 6, the UE registration process may include steps S61 to S64:
  • step S61 the UE sends a registration request to the AMF.
  • step S62 the AMF selects UDM.
  • Step S63 a contract data acquisition process is performed between AMF and UDM.
  • This process may be initiated by AMF to UDM.
  • AMF sends Nudm_SDM_Get to UDM to obtain SMF selection subscription data and UE context, access and mobility subscription data from SMF data.
  • UDM can include the determined service area ID (or also include the applicable service type) in the interaction information with AMF and send it to AMF.
  • AMF then receives the interaction information and obtains the service area ID from it .
  • PCF network functional entities
  • UDM can also send the specified service type and/or time range applicable to the service area ID to the AMF.
  • step S64 the AMF sends a registration acceptance message to the UE.
  • the service area IDs sent and received in the example UE registration process in FIGS. 4-6 above and the applicable service types are valid for all transactions of the UE.
  • the PDU session establishment process includes a session management policy association establishment or modification process
  • the service area identification policy management entity may be a PCF entity
  • the NF entity receiving the service area ID may be a session management function as an example of a network function entity ( Session Management Function (SMF) entity.
  • SMF Session Management Function
  • the PCF entity sends the information containing the determined service area ID to the SMF entity during the establishment or modification of the session management policy association, and the SMF entity receives the information and obtains the service area ID from the information.
  • receiving the second information including the service area identifier sent by the service area identity policy management entity includes: the session management function entity is associated with the session management policy During the establishment or modification process, the second information including the service area identifier sent by the service area identity policy management entity is received.
  • FIG. 7 An example PDU session establishment process is shown in FIG. 7, which only shows some steps related to PDU session establishment, and omits some less related steps, so it is not a complete PDU session establishment process.
  • the PDU session establishment process may include steps S71-S75:
  • step S71 the UE sends a PDU session establishment request to the AMF.
  • step S72 the AMF selects the SMF based on the relevant selection strategy.
  • the AMF performs SMF selection according to the received service area ID in this step.
  • step S73 a session management context establishment or update (Nsmf_PDUSession_CreatSMContext) request and response is sent between AMF and SMF.
  • Nsmf_PDUSession_CreatSMContext a session management context establishment or update
  • step S74 the SMF selects the PCF based on relevant standards.
  • the SMF may select the PCF according to the service area ID.
  • step S75 a session management (SM) policy association establishment or modification process is performed between the SMF and the PCF.
  • SM session management
  • This process may be initiated by the SMF to the PCF, or it may be initiated by other NF entities (such as PCF).
  • PCF can include the determined service area ID (or also include the applicable service type and/or time range) in the interaction information with SMF and send it to SMF , SMF then receives the interaction information and obtains the service area ID from it.
  • the PCF can also send the specified service type and/or time range applicable to the service area ID to the SMF.
  • the service area IDs sent and received during the example PDU session establishment process of FIG. 7 above and their applicable service types are valid for the PDU session of the UE.
  • the disclosure does not limit the name of the service type of the service area ID provided by the PCF, as long as it is the service invocation type of the policy information obtained from the PCF.
  • the service area identification policy management entity determines the service area ID and sends it to other NF entities of the core network, so that the NF entity receiving the service area ID
  • the service producer instance in the corresponding service area can be selected according to the service area ID, thereby effectively using the service area ID and improving the communication efficiency.
  • a network function (NF) entity is also provided.
  • the network function entity may be a network device in the core network that can determine the service area ID and send it to another NF entity.
  • it may be The service area of the core network identifies the policy management entity.
  • FIG. 8 shows a schematic composition block diagram of a network function entity according to an exemplary embodiment of the present disclosure. As shown in the example in FIG. 8, the network function entity 800 may include:
  • the determining module 810 is configured to: determine the service area identifier
  • the sending module 820 is configured to send information containing the service area identifier to another network function entity.
  • the determination module 810 may be configured to determine the service area identifier according to at least one of the following:
  • Requirements of application function AF for example, the AF wants to route user equipment to a certain service area, and the AF entity can send preference information of the service area to the network;
  • Management and O&M operation requirements for example, service producers in a certain area need service upgrades, you can consider routing user equipment to other service areas to reduce the impact of service upgrades on user experience, and then modify the service after the upgrade is complete
  • the area ID method allows user equipment to be rerouted to the service producer of the service area ID).
  • the sending module 820 may be further configured to perform at least one of the following:
  • the second information including the service area identifier is sent to the another network function entity.
  • the network function entity 800 is a policy control function PCF entity
  • the another network function entity includes an access and mobility management function AMF entity
  • the registration process includes an access management policy association establishment process
  • the first information including the service area identifier is sent to the access and mobility management functional entity.
  • the network function entity 800 is a policy control function PCF entity
  • the another network function entity includes an access and mobility management function AMF entity
  • the registration process includes an access management policy update process
  • a sending module 820 can be further configured to:
  • the first information including the service area identifier is sent to the access and mobility management function entity.
  • the network function entity 800 is a unified data management UDM entity
  • the another network function entity includes an access and mobility management function AMF entity
  • the registration process includes a contract data acquisition process
  • the sending module 820 may It is further configured to:
  • the first information including the service area identifier is sent to the access and mobility management function entity.
  • the network function entity 800 is a policy control function PCF entity
  • the another network function entity includes a session management function SMF entity
  • the protocol data unit session establishment process includes a session management policy association establishment or modification process
  • the sending module 820 may be further configured to:
  • the second information including the service area identifier is sent to the session management function entity.
  • the sending module 820 may also be configured to:
  • the time range to which the service area identifier applies is the time range to which the service area identifier applies.
  • the network function entity 800 may further include:
  • the receiving module 830 is configured to receive the application function request from the network open function NEF entity or the application function AF entity.
  • the network function NF entity may be a core network capable of receiving a service area ID from a service area identification policy management entity and selecting a service according to the service area ID
  • the network device of the producer instance may be a mobility management entity or a session management function entity.
  • FIG. 9 shows a schematic composition block diagram of an exemplary embodiment of such a network functional entity. As shown in the example in FIG. 9, the network function entity 900 may include:
  • the receiving module 910 is configured to receive the information including the service area identifier sent by the service area identity policy management entity of the core network;
  • the processing module 920 is configured to acquire the service area identifier from the information and select a service producer instance from the service producer corresponding to the service area identifier.
  • the receiving module 910 may be further configured to:
  • the network function entity 900 may be an access and mobility management function AMF entity, the service area identification policy management entity includes a policy control function PCF entity, and the registration process includes an access management policy association establishment process ,
  • the receiving module 910 may be further configured to:
  • the first information including the service area identifier sent by the policy control function entity is received.
  • the network function entity 900 may be an access and mobility management function AMF entity, the service area identification policy management entity is a policy control function PCF entity, and the registration process includes an access management policy update process,
  • the receiving module 910 may be further configured to:
  • the network function entity 900 may be an access and mobility management function AMF entity
  • the service area identification policy management entity is a unified data management UDM entity
  • the registration process includes a contract data acquisition process
  • a receiving module The 910 can be further configured to:
  • the network function entity 900 may be a session management function SMF entity
  • the service area identification policy management entity is a policy control function PCF entity
  • the protocol data unit session establishment process includes session management policy association establishment or modification
  • the receiving module 910 may be further configured to:
  • receiving second information including the service area identifier sent by the service area identifier policy management entity In the process of establishing or modifying the session management policy association, receiving second information including the service area identifier sent by the service area identifier policy management entity.
  • the processing module 920 may also be configured to:
  • the use priority of the service area identifier included in the second information is set higher than the service area included in the first information The use priority of the logo.
  • the network function entity 900 may be a new network function entity switched from the old network function entity used before, and the receiving module 910 may also be configured as:
  • the processing module 920 may also be configured to set the use priority of the service area identifier from the old network function entity to be lower than the use of the service area identifier contained in the information sent by the service area identity policy management entity priority.
  • the NF entity embodiments in the above embodiments can be implemented by hardware, software, firmware, or a combination thereof, and it can be implemented as a separate device, or each component unit/module is dispersed in one or A logic integrated system that performs corresponding functions in multiple computing devices separately.
  • the units/modules constituting the NF entity in the above embodiments are divided according to logical functions, and they can be re-divided according to logical functions, for example, the device can be implemented by more or fewer units/modules.
  • These constituent units/modules can be implemented by means of hardware, software, firmware, or a combination thereof. They can be separate independent components or integrated units/modules that combine multiple components to perform corresponding logical functions.
  • the hardware, software, firmware, or a combination thereof may include: separate hardware components, functional modules implemented through programming, functional modules implemented through programmable logic devices, etc., or a combination of the above.
  • the NF entity embodiment may be implemented as a network device including a memory and a processor, the memory stores a computer program, and the computer program when executed by the processor So that the network device executes any one of the embodiments of the communication methods described above, or, when the computer program is executed by the processor, causes the network device to implement the NF entity embodiments described above
  • the processor described in the above embodiment may refer to a single processing unit, such as a central processing unit CPU, or may be a distributed processor system including multiple distributed processing units/processors.
  • the memory described in the above embodiment may include one or more memories, which may be internal memories of the computing device, such as various transient or non-transitory memories, or may be connected to the external of the computing device through the memory interface Storage device.
  • FIG. 10 shows a schematic block diagram of an exemplary embodiment of such a network device 1001.
  • the network device may include, but is not limited to, at least one processing unit 1010, at least one storage unit 1020, and a bus 1030 connecting different system components (including the storage unit 1020 and the processing unit 1010).
  • the storage unit stores a program code, and the program code can be executed by the processing unit 1010 so that the processing unit 1010 executes the steps of various exemplary embodiments of the above-described exemplary method of the present specification.
  • the processing unit 1010 may perform various steps as shown in FIGS. 2-6.
  • the storage unit 1020 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 1021 and/or a cache storage unit 1022, and may further include a read-only storage unit (ROM) 1023.
  • RAM random access storage unit
  • ROM read-only storage unit
  • the storage unit 1020 may further include a program/utility tool 1024 having a set of (at least one) program modules 1025.
  • program modules 1025 include but are not limited to: an operating system, one or more application programs, other program modules, and program data. Each of these examples or some combination may include an implementation of the network environment.
  • the bus 1030 may be one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any of a variety of bus structures bus.
  • the network device may also communicate with one or more external devices 1070 (eg, keyboard, pointing device, Bluetooth device, etc.), and may also communicate with one or more devices that enable users to interact with the network device, and/or with The network device can communicate with any device (such as a router, modem, etc.) that communicates with one or more other computing devices. This communication can be performed via an input/output (I/O) interface 1050.
  • the network device can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN) and/or a public network, such as the Internet) through a network adapter 1060. As shown in FIG. 10, the network adapter 1060 communicates with other modules of the network device through the bus 1030.
  • the network device may be implemented using other hardware and/or software modules, including but not limited to: microcode, device driver, redundant processing unit, external disk drive array, RAID system, Tape drives and data backup storage systems, etc.
  • a computer-readable storage medium on which computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor of the computer, the computer is caused to perform the above method Examples of methods described in the Examples section.
  • a program product for implementing the method in the above method embodiment which may adopt a portable compact disk read-only memory (CD-ROM) and include a program code, and may be used in a terminal Devices, such as personal computers.
  • CD-ROM portable compact disk read-only memory
  • the program product of the present disclosure is not limited thereto.
  • the readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, apparatus, or device.
  • the program product may use any combination of one or more readable media.
  • the readable medium may be a readable signal medium or a readable storage medium.
  • the readable storage medium may be, for example but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination of the above. More specific examples of readable storage media (non-exhaustive list) include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing.
  • the computer-readable signal medium may include a data signal that is transmitted in baseband or as part of a carrier wave, in which readable program code is carried. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device.
  • the program code contained on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
  • the program code for performing the operations of the present disclosure can be written in any combination of one or more programming languages including object-oriented programming languages such as Java, C++, etc., as well as conventional procedural formulas Programming language-such as "C" language or similar programming language.
  • the program code may be executed entirely on the user's computing device, partly on the user's device, as an independent software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server To execute.
  • the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (eg, using Internet service provision Business to connect via the Internet).
  • LAN local area network
  • WAN wide area network
  • Internet service provision Business to connect via the Internet
  • the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, U disk, mobile hard disk, etc.) or on a network , Including several instructions to cause a computing device (which may be a personal computer, server, mobile terminal, or network device, etc.) to perform the method according to an embodiment of the present disclosure.
  • a non-volatile storage medium which may be a CD-ROM, U disk, mobile hard disk, etc.
  • a computing device which may be a personal computer, server, mobile terminal, or network device, etc.

Landscapes

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

Abstract

本公开提供了一种通信方法和网络设备。所述通信方法由核心网的服务区标识策略管理实体执行，所述通信方法包括：确定服务区标识；向网络功能实体发送包含所述服务区标识的信息，使得所述网络功能实体从所述服务区标识相对应的服务生产者中选择服务生产者实例。

Description

一种通信方法和网络设备
本申请要求于2018年12月26日提交中国专利局、申请号为201811603214.2、申请名称为“一种通信方法和网络设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本公开涉及通信技术领域，具体涉及一种通信方法、网络功能实体、网络设备和计算机可读存储介质。
发明背景
在5G(第5代)移动通信***的基于服务的体系架构中，服务区标识(服务区ID，service zone ID)被提议用作发现和选择服务生产者实例的元数据之一。服务区ID用于标识服务生产者实例的服务区。服务框架支撑功能(Service Framework Support Function，SFSF)支持基于服务集合ID(SET ID)和服务区ID的组合来发现网络功能(Network Function，NF)服务。服务区ID可用于指示应当从服务区ID标识的特定服务区中的服务集合中选择目标NF服务实例。
服务区ID的含义可以是如下两种含义中的一种：
- 服务区ID表示服务生产者实例的服务区域；
- 服务区ID表示服务生产者实例所部署的区域。
但是，目前的通信协议(TR23.742)中仅指出消费者服务实例可以基于服务区ID选择服务生产者实例，但未提及消费者服务具体应如何获得服务生产者实例的服务区ID。这使得服务区ID在服务框架中的使用受到了限制。
发明内容
本公开的实施例提供一种通信方法、网络功能实体、网络设备和计算机可读存储介质。
根据本公开实施例的第一方面，公开了一种通信方法，所述通信方法由核心网的服务区标识策略管理实体执行，所述通信方法包括：
确定服务区标识；
向网络功能实体发送包含所述服务区标识的信息，使得所述网络功能实体从所 述服务区标识相对应的服务生产者中选择服务生产者实例。
根据本公开实施例的第二方面，公开了一种通信方法，所述通信方法由核心网的网络功能实体执行，所述通信方法包括：
接收核心网的服务区标识策略管理实体发送的包含服务区标识的信息；
从所述信息中获取所述服务区标识；
从所述服务区标识相对应的服务生产者中选择服务生产者实例。
根据本公开实施例的第三方面，公开了一种网络功能实体，包括：
确定模块，其被配置为：确定服务区标识；
发送模块，其被配置为：向另一网络功能实体发送包含所述服务区标识的信息，使得所述另一网络功能实体从所述服务区标识相对应的服务生产者中选择服务生产者实例。
根据本公开实施例的第四方面，公开了一种网络功能实体，包括：
接收模块，其被配置为：接收核心网的服务区标识策略管理实体发送的包含服务区标识的信息；
处理模块，其被配置为：从所述信息中获取所述服务区标识，并从所述服务区标识相对应的服务生产者中选择服务生产者实例。
根据本公开实施例的第五方面，公开了一种网络设备，其包括处理器以及存储器，所述存储器上存储有计算机可读指令，所述计算机可读指令被所述处理器执行时实现在本公开上述实施例中所述的通信方法。
根据本公开实施例的第六方面，公开了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现在本公开上述实施例中所述的通信方法。
在本公开的各实施例中，由核心网的服务区标识策略管理实体确定服务区ID并向其他网络功能实体发送包含服务区ID的信息，使得接收到服务区ID的网络功能实体能够使用该服务区ID来选择服务生产者实例。通过上述各实施例，可以实现根据生产者的服务区域灵活选择服务生产者的能力，同时可以实现对于服务区ID灵活的策略配置和管理，提高了通信效率。
本公开的其他特性和优点将通过下面的详细描述变得显然，或部分地通过本公开的实践而习得。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性的，并不能限制本公开。
附图简要说明
通过参照附图详细描述其示例实施例，本公开的上述和其它特征及优点将变得更加显而易见。此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本申请的实施例，并与说明书一起用于解释本申请的原理。
图1示出了根据本公开一示例性实施例的通信方法的应用环境的架构示意图。
图2示出了根据本公开一示例性实施例的通信方法的流程示意图。
图3示出了根据本公开另一示例性实施例的通信方法的流程示意图。
图4示出了根据本公开一示例性实施例的在UE注册过程中发送和接收服务区ID的示意图。
图5示出了根据本公开另一示例性实施例的在UE注册过程中发送和接收服务区ID的示意图。
图6示出了根据本公开又一示例性实施例的在UE注册过程中发送和接收服务区ID的示意图。
图7示出了根据本公开一示例性实施例的在PDU会话建立过程中发送和接收服务区ID的示意图。
图8示出了根据本公开一示例性实施例的网络功能实体的示意组成框图。
图9示出了根据本公开另一示例性实施例的网络功能实体的示意组成框图。
图10示出了根据本公开一示例性实施例的网络设备的示意组成框图。
实施本发明的方式
现在将参考附图更全面地描述示例实施方式。然而，示例实施方式能够以多种形式实施，且不应被理解为限于在此阐述的范例；相反，提供这些示例实施方式使得本公开的描述将更加全面和完整，并将示例实施方式的构思全面地传达给本领域的技术人员。附图仅为本公开的示意性图解，并非一定是按比例绘制。图中相同的附图标记表示相同或类似的部分，因而将省略对它们的重复描述。
此外，所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多示例实施方式中。在下面的描述中，提供许多具体细节从而给出对本公开的示例实施方式的充分理解。然而，本领域技术人员将意识到，可以实践本公开的技术方案而省略所述特定细节中的一个或更多，或者可以采用其它的方法、组元、步骤等。在其它情况下，不详细示出或描述公知结构、方法、实现或者操作以避免喧宾夺主而 使得本公开的各方面变得模糊。
附图中所示的一些方框图是功能实体，不一定必须与物理或逻辑上独立的实体相对应。可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
图1是根据一示例性实施例示出的本公开的通信方法的应用环境的示意简图。
如图1所示，在5G通信***中，终端设备(User Equipment，UE)110可以通过诸如无线接入网(Radio Access Network，RAN)120的接入网络与核心网130进行通信。核心网130可以包括一个或多个控制面网络功能(Network Function，NF)实体以及一个或多个用户面功能UPF(User Plane Function)实体UPF1 137、UPF2138。所述一个或多个控制面NF实体可以是诸如图1中所示的服务区标识策略管理实体131、移动性管理实体132、会话管理功能(Session Management Function，SMF)实体SMF 139或其他NF实体NF1 133、NF2 134。核心网130可以与一个或多个应用功能(Application Function,AF)实体进行通信。AF实体可以对应运营商的自营业务功能，也可以对应第三方业务提供商提供的业务功能，可以是诸如图1中所示的AF1 135和AF2 136。
图1中所示的架构为服务化的体系架构，各消费者服务可以通过使用一个或多个服务生产者来完成通信过程。服务框架支撑功能支持使用服务区ID来指示应当从服务区ID标识的特定服务区中的服务生产者集合中选择目标NF服务实例。例如，为完成通信，移动性管理实体132可以基于服务区ID从多个其他NF服务实例(例如多个会话管理实体实例)中选择一个或多个NF服务实例来用于通信过程。在根据本公开实施例的技术方案中，本申请的发明人提出了由服务区标识策略管理实体131确定服务区ID并将其发送给网络功能实体(例如移动性管理实体132、会话管理功能实体SMF 139或其他NF实体)，以便网络功能实体可以使用服务区ID来选择服务生产者实例的技术方案。通过本公开的各实施例，能够提供利用服务区ID选择服务生产者实例的完整技术方案，使得通信过程更加高效。
本文中所述的“服务区标识策略管理实体”并不特指具体的某个或某种核心网实体，而是核心网中具有服务区标识策略管理(例如生成服务区标识策略)功能的所有NF实体的统称，例如，其可以包括但不限于核心网的策略控制功能(PCF，Policy Control Function)实体、统一数据管理(UDM，Unified Data Management)实体、核心网的服务化框架内的服务选择策略管理功能等。
相似地，本文中所述的“移动性管理实体”也不特指具体的某个或某种核心网实体，而是核心网中具有移动性管理功能的所有NF实体的统称，例如，其可以包括但不限于接入和移动性管理功能(AMF，Access and Mobility Management Function)实体等。
本文中所述的各种核心网功能实体可以是具有该功能的网络设备或网络设备组合。
本文中所述的“终端设备”或“UE”指可以接入核心网并与其他网络设备或是应用服务器进行通信的任何用户设备，包括手机、平板电脑、笔记本电脑、各种智能家电等。
图1所示及以上描述只是本公开的通信方法所涉及的实施环境的示例性实施例，可以理解的是，适用于本公开实施例的实施环境存在多种变形。
图2示出了根据本公开一示例性实施例的通信方法的流程示意图。该示例方法可以由服务区标识策略管理实体来执行。换而言之，图2中所示的通信方法实施例是在服务区标识策略管理实体侧执行的技术方案。如图2所示，该示例方法包括步骤S210～S220：
步骤S210，确定服务区标识。
服务区标识策略管理实体可以通过多种方式来确定服务区ID，例如，可以从其他核心网实体接收服务区标识，也可以基于已知信息生成或选择服务区ID。
在一个示例中，服务区标识策略管理实体根据如下信息中的至少一个来确定所述服务区ID：运营商的策略；应用功能(AF)的要求(例如，该AF希望把用户设备路由到某个服务区域，通过AF实体可以发送该服务区的偏好信息给网络)；本地配置数据；管理和运维操作要求(例如，某个区域的服务生产者需要业务升级，可以考虑把用户设备路由到其他服务区域中，以减少业务升级对用户体验的影响，等升级完成后再通过修改服务区ID的方式，让用户设备可以重新路由到该服务区ID的服务生产者上)。
服务区标识策略管理实体可以基于如上所述信息中的一种或几种实时确定并发送服务区ID，也可以在获得如上所述的各项信息后预先确定服务区ID并实时或基于请求发送确定出的服务区ID。
服务区标识策略管理实体可以获取以上各项信息中的至少一个并基于所获取的信息确定服务区ID。例如，策略控制功能PCF实体根据配置数据以及管理和运维操作要求确定服务区ID，以将确定出的服务区ID用于为UE的相关消费者服务 实例确定服务生产者实例。又例如，统一数据管理UDM实体根据诸如UE的签约数据的配置数据确定服务区ID，以将其用于为UE的相关消费者服务实例确定服务生产者实例。又例如，服务化框架中负责服务选择策略的功能根据网络管理和运维操作要求确定某服务的服务区ID，将其用于为该服务实例下的UE确定服务生产者实例。
在一个示例中，AF如果想影响服务生产者实例的选择，可以通过AF实体将偏好使用的服务区ID或服务区偏好信息包括在请求中发送给网络开放功能(NEF，Network Exposure Function)实体，由NEF实体来决定是否要接受该请求。如果决定接受请求，则NEF实体将请求中携带的偏好信息提供给服务区标识策略管理实体，以供服务区标识策略管理实体在确定服务区ID时使用。或者，运营商设备或AF实体可以将偏好信息直接发送给服务区标识策略管理实体。
在一个示例中，确定服务区ID还包括确定该服务区ID所适用的服务类型和/或时间范围。即，指定在选择哪些服务类型时使用该服务区ID。
步骤S220，向网络功能实体发送包含所述服务区标识的信息，使得所述网络功能实体从所述服务区标识相对应的服务生产者中选择服务生产者实例。
步骤S220中的网络功能实体可以指能够使用服务区ID选择服务生产者实例的任何核心网实体，例如，移动性管理实体、SMF实体或其他网络功能实体。
服务区标识策略管理实体可以在通信过程中将步骤S210中确定出的服务区ID携带在其他信息中一起发送给另一网络功能实体(例如移动性管理实体)。例如，可以在终端设备UE的注册过程中向网络功能实体发送包含服务区ID的第一信息，或者在终端设备的协议数据单元(PDU，Protocol Data Unit)会话建立(PDU Session Establishment)过程中，向网络功能实体发送包含服务区ID的第二信息。或者，还可以既在UE注册过程中发送，又在PDU会话建立过程中发送，其中，可以将在PDU会话建立过程中发送的服务区ID的使用优先级设置为高于在UE注册过程中发送的服务区ID的使用优先级，即，网络功能实体在接收到所述第一信息和所述第二信息二者的情况下，优先使用第二信息中包含的服务区ID，即优先使用在PDU会话建立过程中发送的服务区ID。
在一个示例中，服务区标识策略管理实体除了发送服务区ID，还可以发送如下中的至少一个：服务区ID所适用的服务类型；服务区ID所适用的时间范围。例如，可以发送包含服务区标识以及所述服务区标识所适用的服务类型两者的信息。NF实体如果收到了服务区ID以及其所适用的指定服务类型，则可以将该服务区ID用 于指定的服务类型。在一些示例中，如果仅收到服务区ID而没有收到服务区ID所适用的服务类型，则可以将该服务区ID用于所有服务类型。
图3示出了根据本公开另一示例性实施例的通信方法的流程示意图。该示例方法可以由核心网的NF实体(例如移动性管理实体、会话管理实体或其他NF实体)来执行。换而言之，图3中所示的通信方法实施例是在接收实体侧(例如移动性管理实体侧)执行的技术方案。如图3所示，该示例方法包括步骤S310～S330：
步骤S310，接收核心网的服务区标识策略管理实体发送的包含服务区标识的信息。
NF实体可以在与服务区标识策略管理实体的通信过程中接收包含服务区ID的信息。例如，在终端设备的注册过程中，接收所述服务区标识策略管理实体发送的包含服务区标识的第一信息；或者在终端设备的协议数据单元会话建立过程中，接收所述服务区标识策略管理实体发送的包含服务区标识的第二信息；或者，既在UE注册过程中接收，又在PDU会话建立过程中接收，其中，可以将在PDU会话建立过程中接收的服务区ID的使用优先级设置为高于在UE注册过程中接收的服务区ID的使用优先级，即，优先使用在PDU会话建立过程中接收的服务区ID。
步骤S320，从所述信息中获取所述服务区标识。
例如，可以通过检索信息中相关的指定字段来获取其中携带的服务区ID。
步骤S330，从所述服务区标识相对应的服务生产者中选择服务生产者实例。
如前所述，服务消费者在发送服务调用请求时将服务区ID发送给SFSF,SFSF支持根据服务区ID从特定服务区的服务集合中选择服务生产者实例。网络功能实体在接收到服务区标识策略管理实体发送的包含服务区ID的信息后，可以从该信息中获取服务区ID，并根据该服务区ID选择对应该服务区ID的服务生产者。如果收到了服务区ID及其适用的指定服务类型，则网络功能实体可以将该服务区ID用于选择指定的服务类型的服务生产者。如果仅收到服务区ID而没有收到服务区ID所适用的服务类型，则可以将该服务区ID用于所有服务类型的服务生产者的选择。
在一个示例中，所述网络功能实体包括新网络功能实体以及在此之前使用的旧网络功能实体，从而可能发生服务于UE的新、旧NF实体之间的切换，即，从旧NF实体切换到新NF实体。在这种情况下，可以使旧NF实体将接收到的、仍然有效的服务区ID(以及指定服务类型)信息传送给新NF实体，新NF实体接收来自所述旧网络功能实体的服务区ID并继续使用。其中，如果新NF实体从服务区标识策略管理实体接收到新的服务区ID信息，则可以将从旧NF实体收到的服务区ID 的使用优先级设置为低于从服务区标识策略管理实体收到的服务区ID的使用优先级。或者，新NF实体用从服务区标识策略管理实体接收到的新的服务区ID信息来覆盖从旧NF实体接收到的服务区ID信息。
在一个示例中，NF实体可以将接收到的服务区ID(以及指定服务类型和/或适用的时间范围)传送给需要的其他NF实体(例如从AMF传送给SMF)。
图4示出了根据本公开一示例性实施例的在UE注册过程中发送和接收服务区ID的示意图。在该示例中，UE注册过程包括接入管理策略关联建立(Access Management Policy Association Establishment)过程，服务区标识策略管理实体可以是策略控制功能PCF实体，接收服务区ID的NF实体可以是作为移动性管理实体的示例的AMF实体。如图4所示，PCF实体在接入管理策略关联建立过程中向AMF实体发送包含确定出的服务区ID的信息，AMF实体接收该信息并从中获取服务区ID。因此，上述的在终端设备的注册过程中，接收所述服务区标识策略管理实体发送的包含服务区标识的第一信息包括：所述接入和移动性管理功能实体在所述接入管理策略关联建立过程中接收所述策略控制功能实体发送的包含服务区标识的第一信息。
在图4中示出了一种示例UE注册过程，该过程只示出了一些与UE注册比较相关的步骤，而省略掉一些不太相关的步骤。如图4所示，UE注册过程可以包括步骤S41～S44：
步骤S41，UE向AMF发出注册请求。
步骤S42，AMF选择PCF。
步骤S43，在AMF与PCF之间执行接入管理(AM，Access Management)策略关联建立过程。本公开对该流程和策略的名称不作限定，只要是从PCF获取的用户的移动性管理策略的服务调用类型均可适用。
该过程可以是AMF向PCF发起的。可以理解的是，该过程也可以由其他实体(例如PCF)发起，本公开对此不作限制。在该过程中，AMF与PCF之间有信息交互，PCF可以将所确定出的服务区ID(或者还包括所适用的服务类型和/或时间范围)包含在与AMF的交互信息中发送给AMF，AMF继而接收该交互信息并从中获取服务区ID。
除了服务区ID，PCF还可以将服务区ID适用的指定服务类型和/或时间范围发送给AMF。例如，在该过程中PCF发送给AMF的信息中包含：
-Service Zone ID：1
Service type：ServiceType 1，ServiceType 2
-Service Zone ID：2
Service type：ServiceType 3，ServiceType 4
在上面的信息示例中，包含服务区ID 1和2，并且指定了服务区ID 1的服务类型为服务类型1和2，服务区ID 2的服务类型为服务类型3和4。收到这样的信息后，AMF在选择服务类型1或服务类型2的服务生产者时，会选择服务区ID为1的服务区中的服务生产者实例，而在选择服务类型3或服务类型4的服务生产者时，会选择服务区ID为2的服务区中的服务生产者实例。对于其他服务类型，AMF会选择具有任意服务区ID的服务生产者实例。该信息示例也适用于本文下面所述的其他实施例。
步骤S44，AMF向UE发送注册接受消息。
图5示出了根据本公开另一示例性实施例的在UE注册过程中发送和接收服务区ID的示意图。在该示例中，UE注册过程包括接入管理策略更新过程，服务区标识策略管理实体可以是策略控制功能PCF实体，接收服务区ID的NF实体可以是作为移动性管理实体的示例的AMF实体。如图5所示，PCF实体在接入管理策略更新过程中向AMF实体发送包含确定出的服务区ID的信息，AMF实体接收该信息并从中获取服务区ID。因此，上述的在终端设备的注册过程中，接收所述服务区标识策略管理实体发送的包含服务区标识的第一信息包括：所述接入和移动性管理功能实体在所述接入管理策略更新过程中接收所述策略控制功能实体发送的包含服务区标识的第一信息。
在图5中示出了一种示例UE注册过程，该过程只示出了一些与UE注册比较相关的步骤，而省略掉一些不太相关的步骤。如图5所示，UE注册过程可以包括步骤S51～S55：
步骤S51，UE向AMF发出注册请求。
步骤S52，AMF选择PCF。
步骤S53，AMF向UE发送注册接受消息。
步骤S54，在AMF与PCF之间执行接入管理策略更新过程。
该过程可以是AMF向PCF发起的。可以理解的是，该过程也可以由其他实体(例如PCF)发起，本公开对此不作限制。该过程可以在终端设备策略关联建立(UE Policy Association Establishment)过程之后进行，也可以和终端设备策略关联建立过程并行执行。在该过程中，AMF与PCF之间有信息交互，PCF可以将所确定出的 服务区ID(或者还包括所适用的服务类型和/或时间范围)包含在与AMF的交互信息中发送给AMF，AMF继而接收该交互信息并从中获取服务区ID。
除了服务区ID，PCF还可以将服务区ID适用的指定服务类型和/或时间范围发送给AMF。
步骤S55，注册完成。
只要UE没发生去附着(De-registration)过程，在上面图4和图5的示例UE注册过程中发送和接收的服务区ID及其适用的服务类型对该UE在去附着之前的所有交易(transaction)都有效。
图6示出了根据本公开又一示例性实施例的在UE注册过程中发送和接收服务区ID的示意图。在该示例中，UE注册过程包括签约数据获取过程，服务区标识策略管理实体可以是统一数据管理UDM实体，接收服务区ID的NF实体可以是作为移动性管理实体的示例的AMF实体。如图6所示，UDM实体在签约数据获取过程中向AMF实体发送包含确定出的服务区ID的信息，AMF实体接收该信息并从中获取服务区ID。因此，上述的在终端设备的注册过程中，接收所述服务区标识策略管理实体发送的包含服务区标识的第一信息包括：所述接入和移动性管理功能实体在所述签约数据获取过程中接收所述统一数据管理实体发送的包含服务区标识的第一信息。
在图6中示出了一种示例UE注册过程，该过程只示出了一些与UE注册比较相关的步骤，而省略掉一些不太相关的步骤。如图6所示，UE注册过程可以包括步骤S61～S64：
步骤S61，UE向AMF发出注册请求。
步骤S62，AMF选择UDM。
步骤S63，在AMF与UDM之间执行签约数据获取过程。
该过程可以是AMF向UDM发起的。例如如图6所示，AMF向UDM发送Nudm_SDM_Get，以从SMF数据中获取SMF选择签约数据和UE上下文、接入和移动性签约数据。作为对Nudm_SDM_Get的响应，UDM可以将所确定出的服务区ID(或者还包括所适用的服务类型)包含在与AMF的交互信息中发送给AMF，AMF继而接收该交互信息并从中获取服务区ID。可以理解的是，该过程也可以由其他网络功能实体(例如PCF)发起，本公开对此不作限制。本公开对UDM提供的服务类型的名称不作限定，只要是从UDM获取的用户的签约信息的服务调用类型均可适用。
除了服务区ID，UDM还可以将服务区ID适用的指定服务类型和/或时间范围发送给AMF。
步骤S64，AMF向UE发送注册接受消息。
在一个示例中，只要UE没发生重新注册，在上面图4-6的示例UE注册过程中发送和接收的服务区ID及其适用的服务类型对该UE的所有交易(transaction)都有效。
图7示出了根据本公开一示例性实施例的在PDU会话建立过程中发送和接收服务区ID的示意图。在该示例中，PDU会话建立过程包括会话管理策略关联建立或修改过程，服务区标识策略管理实体可以是PCF实体，接收服务区ID的NF实体可以是作为网络功能实体的示例的会话管理功能(Session Management Function，SMF)实体。如图7所示，PCF实体在会话管理策略关联建立或修改过程中向SMF实体发送包含确定出的服务区ID的信息，SMF实体接收该信息并从中获取服务区ID。因此，上述的在终端设备的协议数据单元会话建立过程中，接收所述服务区标识策略管理实体发送的包含服务区标识的第二信息包括：所述会话管理功能实体在所述会话管理策略关联建立或修改过程中接收所述服务区标识策略管理实体发送的包含服务区标识的第二信息。
在图7中示出了一种示例PDU会话建立过程，该过程只示出了一些与PDU会话建立比较相关的步骤，而省略掉一些不太相关的步骤，因此并非完整的PDU会话建立流程。如图7所示，PDU会话建立过程可以包括步骤S71～S75：
步骤S71，UE向AMF发出PDU会话建立请求。
步骤S72，AMF基于相关选择策略选择SMF。
如果在UE注册过程中已经接收到了用于该UE的这种服务类型的服务区ID，则AMF在该步骤中根据所接收到的该服务区ID进行SMF选择。
步骤S73，在AMF和SMF之间发送会话管理上下文建立或更新(Nsmf_PDUSession_CreatSMContext)请求与响应。
步骤S74，SMF基于相关标准选择PCF。
如果SMF知晓在UE注册过程中收到的用于这种服务类型的服务区ID，则SMF可以根据该服务区ID选择PCF。
步骤S75，在SMF与PCF之间执行会话管理(Session Management，SM)策略关联建立或修改过程。
该过程可以是SMF向PCF发起的，也可以是其他NF实体(例如PCF)发起 的。在该过程中，SMF与PCF之间有信息交互，PCF可以将所确定出的服务区ID(或者还包括所适用的服务类型和/或时间范围)包含在与SMF的交互信息中发送给SMF，SMF继而接收该交互信息并从中获取服务区ID。
除了服务区ID，PCF还可以将服务区ID适用的指定服务类型和/或时间范围发送给SMF。
在一个示例中，在上面图7的示例PDU会话建立过程中发送和接收的服务区ID及其适用的服务类型对该UE的该PDU会话是有效的。
本公开对PCF提供的服务区ID的服务类型的名称不作限定，只要是从PCF获取的策略信息的服务调用类型均可适用。
通过如上所述的根据本公开各实施例的示例通信方法，提供了由服务区标识策略管理实体确定服务区ID并发送给核心网的其他NF实体的技术方案，使得接收服务区ID的NF实体可以根据服务区ID选择相应服务区中的服务生产者实例，从而实现了对服务区ID的有效利用，提高了通信效率。
根据本公开实施例的另一方面，还提供一种网络功能(NF)实体，该网络功能实体可以是核心网中能够确定服务区ID并发送给另一NF实体的网络设备，例如，可以是核心网的服务区标识策略管理实体。图8示出了根据本公开一示例性实施例的网络功能实体的示意组成框图。如图8中的示例所示，该网络功能实体800可以包括：
确定模块810，其被配置为：确定服务区标识；
发送模块820，其被配置为：向另一网络功能实体发送包含所述服务区标识的信息。
根据一示例性实施例，确定模块810可以被配置为根据如下中的至少一个来确定所述服务区标识：
运营商的策略；
应用功能AF的要求(例如，该AF希望把用户设备路由到某个服务区域，通过AF实体可以发送服务区的偏好信息给网络)；
本地配置数据；
管理和运维操作要求(例如，某个区域的服务生产者需要业务升级，可以考虑把用户设备路由到其他服务区域中，以减少业务升级对用户体验的影响，等升级完成后再通过修改服务区ID的方式，让用户设备可以重新路由到该服务区ID的服务生产者上)。
根据一示例性实施例，发送模块820可以进一步被配置为执行如下中的至少一个：
在终端设备的注册过程中，向所述另一网络功能实体发送包含服务区标识的第一信息；
在终端设备的协议数据单元会话建立过程中，向所述另一网络功能实体发送包含服务区标识的第二信息。
根据一示例性实施例，网络功能实体800为策略控制功能PCF实体，所述另一网络功能实体包括接入和移动性管理功能AMF实体，所述注册过程包括接入管理策略关联建立过程，发送模块820可以进一步被配置为：
在所述接入管理策略关联建立过程中向所述接入和移动性管理功能实体发送包含服务区标识的第一信息。
根据一示例性实施例，网络功能实体800为策略控制功能PCF实体，所述另一网络功能实体包括接入和移动性管理功能AMF实体，所述注册过程包括接入管理策略更新过程，发送模块820可以进一步被配置为：
在所述接入管理策略更新过程中向所述接入和移动性管理功能实体发送包含服务区标识的第一信息。
根据一示例性实施例，网络功能实体800为统一数据管理UDM实体，所述另一网络功能实体包括接入和移动性管理功能AMF实体，所述注册过程包括签约数据获取过程，发送模块820可以进一步被配置为：
在所述签约数据获取过程中向所述接入和移动性管理功能实体发送包含服务区标识的第一信息。
根据一示例性实施例，网络功能实体800为策略控制功能PCF实体，所述另一网络功能实体包括会话管理功能SMF实体，所述协议数据单元会话建立过程包括会话管理策略关联建立或修改过程，发送模块820可以被进一步配置为：
在所述会话管理策略关联建立或修改过程中向所述会话管理功能实体发送包含服务区标识的第二信息。
根据一示例性实施例，发送模块820还可以被配置为：
向所述另一网络功能实体发送包含如下中的至少一个的信息：
所述服务区标识所适用的服务类型；
所述服务区标识所适用的时间范围。
根据一示例性实施例，网络功能实体800还可以包括：
接收模块830，其被配置为：接收来自网络开放功能NEF实体或应用功能AF实体的所述应用功能的要求。
根据本公开实施例的另一方面，还提供另一种网络功能NF实体，该网络功能NF实体可以是核心网中能够接收来自服务区标识策略管理实体的服务区ID并根据服务区ID选择服务生产者实例的网络设备，例如，可以是移动性管理实体或会话管理功能实体。图9示出了这样的网络功能实体的一示例性实施例的示意组成框图。如图9中的示例所示，该网络功能实体900可以包括：
接收模块910，其被配置为接收核心网的服务区标识策略管理实体发送的包含服务区标识的信息；
处理模块920，其被配置为：从所述信息中获取所述服务区标识，并从所述服务区标识相对应的服务生产者中选择服务生产者实例。
根据一示例性实施例，接收模块910可以进一步被配置为：
在终端设备的注册过程中，接收所述服务区标识策略管理实体发送的包含服务区标识的第一信息；
在终端设备的协议数据单元会话建立过程中，接收所述服务区标识策略管理实体发送的包含服务区标识的第二信息。
根据一示例性实施例，网络功能实体900可以是接入和移动性管理功能AMF实体，所述服务区标识策略管理实体包括策略控制功能PCF实体，所述注册过程包括接入管理策略关联建立过程，接收模块910可以被进一步配置为：
在所述接入管理策略关联建立过程中接收所述策略控制功能实体发送的包含服务区标识的第一信息。
根据一示例性实施例，网络功能实体900可以是接入和移动性管理功能AMF实体，所述服务区标识策略管理实体为策略控制功能PCF实体，所述注册过程包括接入管理策略更新过程，接收模块910可以被进一步配置为：
在所述终端设备的接入管理策略更新过程中接收所述策略控制功能实体发送的包含服务区标识的第一信息。
根据一示例性实施例，网络功能实体900可以是接入和移动性管理功能AMF实体，所述服务区标识策略管理实体为统一数据管理UDM实体，所述注册过程包括签约数据获取过程，接收模块910可以被进一步配置为：
在所述签约数据获取过程中接收所述统一数据管理实体发送的包含服务区标识的第一信息。
根据一示例性实施例，网络功能实体900可以是会话管理功能SMF实体，所述服务区标识策略管理实体为策略控制功能PCF实体，所述协议数据单元会话建立过程包括会话管理策略关联建立或修改过程，接收模块910可以被进一步配置为：
在所述会话管理策略关联建立或修改过程中接收所述服务区标识策略管理实体发送的包含服务区标识的第二信息。
根据一示例性实施例，处理模块920还可以被配置为：
在所述接收模块接收到所述第一信息和所述第二信息二者的情况下，将第二信息中包含的服务区标识的使用优先级设置为高于第一信息中包含的服务区标识的使用优先级。
根据一示例性实施例，网络功能实体900可以是从在此之前使用的旧网络功能实体切换到的新网络功能实体，接收模块910还可以被配置为：
接收来自所述旧网络功能实体获取到的选择服务生产者的服务区标识，
处理模块920还可以被配置为：将来自所述旧网络功能实体的服务区标识的使用优先级设置为低于所述服务区标识策略管理实体发送的所述信息中包含的服务区标识的使用优先级。
上述网络功能实体中各个单元/模块的功能和作用的实现过程以及相关细节具体详见上述方法实施例中对应步骤的实现过程，在此不再赘述。
以上各实施例中的NF实体实施例可以通过硬件、软件、固件或其组合的方式来实现，并且其可以被实现为一个单独的装置，也可以被实现为各组成单元/模块分散在一个或多个计算设备中并分别执行相应功能的逻辑集成***。
以上各实施例中组成NF实体的各单元/模块是根据逻辑功能而划分的，它们可以根据逻辑功能被重新划分，例如可以通过更多或更少的单元/模块来实现该装置。这些组成单元/模块分别可以通过硬件、软件、固件或其组合的方式来实现，它们可以是分别的独立部件，也可以是多个组件组合起来执行相应的逻辑功能的集成单元/模块。所述硬件、软件、固件或其组合的方式可以包括：分离的硬件组件，通过编程方式实现的功能模块、通过可编程逻辑器件实现的功能模块，等等，或者以上方式的组合。
根据一个示例性实施例，NF实体实施例可被实现为一种网络设备，该网络设备包括存储器和处理器，所述存储器中存储有计算机程序，所述计算机程序在被所述处理器执行时，使得所述网络设备执行如上所述的各通信方法实施例中的任一个方法，或者，所述计算机程序在被所述处理器执行时使得该网络设备实现如上所述 的各NF实体实施例的组成单元/模块所实现的功能。
上面的实施例中所述的处理器可以指单个的处理单元，如中央处理单元CPU，也可以是包括多个分散的处理单元/处理器的分布式处理器***。
上面的实施例中所述的存储器可以包括一个或多个存储器，其可以是计算设备的内部存储器，例如暂态或非暂态的各种存储器，也可以是通过存储器接口连接到计算设备的外部存储装置。
图10示出了这样的网络设备1001的一个示例性实施例的示意组成框图。如图10所示，该网络设备可以包括但不限于：至少一个处理单元1010、至少一个存储单元1020、连接不同***组件(包括存储单元1020和处理单元1010)的总线1030。
所述存储单元存储有程序代码，所述程序代码可以被所述处理单元1010执行，使得所述处理单元1010执行本说明书上述示例性方法的各种示例性实施方式的步骤。例如，所述处理单元1010可以执行如图2-6中所示的各个步骤。
存储单元1020可以包括易失性存储单元形式的可读介质，例如随机存取存储单元(RAM)1021和/或高速缓存存储单元1022，还可以进一步包括只读存储单元(ROM)1023。
存储单元1020还可以包括具有一组(至少一个)程序模块1025的程序/实用工具1024，这样的程序模块1025包括但不限于：操作***、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络环境的实现。
总线1030可以为表示几类总线结构中的一种或多种，包括存储单元总线或者存储单元控制器、***总线、图形加速端口、处理单元或者使用多种总线结构中的任意总线结构的局域总线。
该网络设备也可以与一个或多个外部设备1070(例如键盘、指向设备、蓝牙设备等)通信，还可与一个或者多个使得用户能与该网络设备交互的设备通信，和/或与使得该网络设备能与一个或多个其它计算设备进行通信的任何设备(例如路由器、调制解调器等等)通信。这种通信可以通过输入/输出(I/O)接口1050进行。并且，该网络设备还可以通过网络适配器1060与一个或者多个网络(例如局域网(LAN)，广域网(WAN)和/或公共网络，例如因特网)通信。如图10所示，网络适配器1060通过总线1030与该网络设备的其它模块通信。应当明白，尽管图中未示出，但该网络设备可以使用其它硬件和/或软件模块来实现，包括但不限于：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID***、磁带驱动器 以及数据备份存储***等。
在本公开的示例性实施例中，还提供了一种计算机可读存储介质，其上存储有计算机可读指令，当所述计算机可读指令被计算机的处理器执行时，使计算机执行上述方法实施例部分描述的各方法实施例。
根据本公开的一个实施例，还提供了一种用于实现上述方法实施例中的方法的程序产品，其可以采用便携式紧凑盘只读存储器(CD-ROM)并包括程序代码，并可以在终端设备，例如个人电脑上运行。然而，本公开的程序产品不限于此，在本文件中，可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行***、装置或者器件使用或者与其结合使用。
所述程序产品可以采用一个或多个可读介质的任意组合。可读介质可以是可读信号介质或者可读存储介质。可读存储介质例如可以为但不限于电、磁、光、电磁、红外线、或半导体的***、装置或器件，或者任意以上的组合。可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。
计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了可读程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。可读信号介质还可以是可读存储介质以外的任何可读介质，该可读介质可以发送、传播或者传输用于由指令执行***、装置或者器件使用或者与其结合使用的程序。
可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于无线、有线、光缆、RF等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言的任意组合来编写用于执行本公开操作的程序代码，所述程序设计语言包括面向对象的程序设计语言—诸如Java、C++等，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算设备上执行、部分地在用户设备上执行、作为一个独立的软件包执行、部分在用户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。在涉及远程计算设备的情形中，远程计算设备可以通过任意种类的网络，包括局域网(LAN)或广域网(WAN)，连接到用户计算设备，或者，可以连接到外部计算设备(例如利用因特网服务提供商来通过因特网连接)。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本公开的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
此外，尽管在附图中以特定顺序描述了本公开中方法的各个步骤，但是，这并非要求或者暗示必须按照该特定顺序来执行这些步骤，或是必须执行全部所示的步骤才能实现期望的结果。附加的或备选的，可以省略某些步骤，将多个步骤合并为一个步骤执行，以及/或者将一个步骤分解为多个步骤执行等。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本公开实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中或网络上，包括若干指令以使得一台计算设备(可以是个人计算机、服务器、移动终端、或者网络设备等)执行根据本公开实施方式的方法。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由所附的权利要求指出。

Claims (17)

  1. 一种通信方法，由核心网的服务区标识策略管理实体执行，包括：
    确定服务区标识；
    向网络功能实体发送包含所述服务区标识的信息，使得所述网络功能实体从所述服务区标识相对应的服务生产者中选择服务生产者实例。
  2. 根据权利要求1所述的方法，其中，所述确定服务区标识包括：根据如下中的至少一个来确定所述服务区标识：
    运营商的策略；
    应用功能的要求；
    本地配置数据；
    管理和运维操作要求。
  3. 根据权利要求1所述的方法，其中，所述向网络功能实体发送包含所述服务区标识的信息包括如下中的至少一个：
    在终端设备的注册过程中，向所述网络功能实体发送包含服务区标识的第一信息；
    在终端设备的协议数据单元会话建立过程中，向所述网络功能实体发送包含服务区标识的第二信息。
  4. 根据权利要求1所述的方法，其中，所述服务区标识策略管理实体包括：服务化框架内的服务选择策略管理功能、策略控制功能实体或统一数据管理实体。
  5. 根据权利要求3所述的方法，其中，所述网络功能实体包括接入和移动性管理功能实体，所述服务区标识策略管理实体包括策略控制功能实体，所述注册过程包括接入管理策略关联建立过程，所述在终端设备的注册过程中，向所述网络功能实体发送包含服务区标识的第一信息包括：
    所述策略控制功能实体在所述接入管理策略关联建立过程中向所述接入和移动性管理功能实体发送包含服务区标识的第一信息。
  6. 根据权利要求3所述的方法，其中，所述网络功能实体包括接入和移动性管理功能实体，所述服务区标识策略管理实体包括策略控制功能实体，所述注册过程包括接入管理策略更新过程，所述在终端设备的注册过程中，向所述网络功能实体发送包含服务区标识的第一信息包括：
    所述策略控制功能实体在所述接入管理策略更新过程中向所述接入和移动性管 理功能实体发送包含服务区标识的第一信息。
  7. 根据权利要求3所述的方法，其中，所述网络功能实体包括接入和移动性管理功能实体，所述服务区标识策略管理实体包括统一数据管理实体，所述注册过程包括签约数据获取过程，所述在终端设备的注册过程中，向所述网络功能实体发送包含服务区标识的第一信息包括：
    所述统一数据管理实体在所述签约数据获取过程中向所述接入和移动性管理功能实体发送包含服务区标识的第一信息。
  8. 根据权利要求3所述的方法，其中，所述网络功能实体包括会话管理功能实体，所述服务区标识策略管理实体包括策略控制功能实体，所述协议数据单元会话建立过程包括会话管理策略关联建立或修改过程，所述在终端设备的协议数据单元会话建立过程中，向所述网络功能实体发送包含服务区标识的第二信息包括：
    所述策略控制功能实体在所述会话管理策略关联建立或修改过程中向所述会话管理功能实体发送包含服务区标识的第二信息。
  9. 根据权利要求1所述的方法，其中，所述向网络功能实体发送包含所述服务区标识的信息包括：向所述网络功能实体发送包含所述服务区标识以及如下中的至少一个的信息：
    所述服务区标识所适用的服务类型的信息；
    所述服务区标识所适用的时间范围。
  10. 根据权利要求2所述的方法，其中，还包括：
    接收来自网络开放功能实体或应用功能实体的所述应用功能的要求。
  11. 一种通信方法，由核心网的网络功能实体执行，包括：
    接收核心网的服务区标识策略管理实体发送的包含服务区标识的信息；
    从所述信息中获取所述服务区标识；
    从所述服务区标识相对应的服务生产者中选择服务生产者实例。
  12. 一种网络功能实体，包括：
    确定模块，其被配置为：确定服务区标识；
    发送模块，其被配置为：向另一网络功能实体发送包含所述服务区标识的信息，使得所述另一网络功能实体从所述服务区标识相对应的服务生产者中选择服务生产者实例。
  13. 根据权利要求12所述的网络功能实体，其中，所述确定模块被配置为根据如下中的至少一个来确定所述服务区标识：
    运营商的策略；
    应用功能的要求；
    本地配置数据；
    管理和运维操作要求。
  14. 根据权利要求12所述的网络功能实体，其中，所述发送模块进一步被配置为执行如下中的至少一个：
    在终端设备的注册过程中，向所述另一网络功能实体发送包含服务区标识的第一信息；
    在终端设备的协议数据单元会话建立过程中，向所述另一网络功能实体发送包含服务区标识的第二信息。
  15. 一种网络功能实体，包括：
    接收模块，其被配置为：接收核心网的服务区标识策略管理实体发送的包含服务区标识的信息；
    处理模块，其被配置为：从所述信息中获取所述服务区标识，并从所述服务区标识相对应的服务生产者中选择服务生产者实例。
  16. 一种网络设备，包括处理器以及存储器，所述存储器上存储有计算机可读指令，所述计算机可读指令被所述处理器执行时实现如权利要求1-11中任一项所述的通信方法。
  17. 一种计算机可读存储介质，存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-11中任一项所述的通信方法。
PCT/CN2019/122414 2018-12-26 2019-12-02 一种通信方法和网络设备 WO2020134885A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020217008747A KR102480207B1 (ko) 2018-12-26 2019-12-02 통신 방법 및 네트워크 디바이스
EP19904490.0A EP3905834B1 (en) 2018-12-26 2019-12-02 Communication method and network device
JP2021526259A JP7162135B2 (ja) 2018-12-26 2019-12-02 通信方法、ネットワーク機能エンティティ、ネットワークデバイスおよびコンピュータプログラム
US17/204,301 US11595797B2 (en) 2018-12-26 2021-03-17 Communication method and network device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811603214.2A CN109548178B (zh) 2018-12-26 2018-12-26 一种通信方法和网络设备
CN201811603214.2 2018-12-26

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/204,301 Continuation US11595797B2 (en) 2018-12-26 2021-03-17 Communication method and network device

Publications (1)

Publication Number Publication Date
WO2020134885A1 true WO2020134885A1 (zh) 2020-07-02

Family

ID=65858384

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/122414 WO2020134885A1 (zh) 2018-12-26 2019-12-02 一种通信方法和网络设备

Country Status (6)

Country Link
US (1) US11595797B2 (zh)
EP (1) EP3905834B1 (zh)
JP (1) JP7162135B2 (zh)
KR (1) KR102480207B1 (zh)
CN (2) CN114375069B (zh)
WO (1) WO2020134885A1 (zh)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114375069B (zh) * 2018-12-26 2024-04-12 腾讯科技（深圳）有限公司 一种通信方法和网络设备
CN111770490B (zh) * 2019-04-02 2022-08-05 大唐移动通信设备有限公司 一种确定终端行为分析的方法和设备
CN113940042B (zh) * 2019-06-14 2023-06-16 华为技术有限公司 用于网络数据分析功能的操作的方法和设备
CN114208136A (zh) * 2019-08-08 2022-03-18 三星电子株式会社 用于无线通信***中通信服务的意图驱动部署和管理的方法和***
CN112637785B (zh) * 2019-10-08 2022-04-29 华为技术有限公司 用于多播传输的方法和装置
EP4057657A4 (en) * 2019-11-08 2023-11-22 LG Electronics Inc. NETWORK CONTROL METHOD FOR EU POLICY TRANSMISSION
EP4097950A1 (en) * 2020-01-31 2022-12-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for including dynamic service areas in access & mobility restriction control
CN113810517B (zh) * 2020-03-17 2023-11-21 腾讯科技（深圳）有限公司 多链路设备mac地址管理方法和多链路设备
CN113498057A (zh) * 2020-04-03 2021-10-12 华为技术有限公司 通信***、方法及装置
US12022545B2 (en) * 2020-07-27 2024-06-25 T-Mobile Usa, Inc. Dynamic PCRF/PCF selection
CN116801194A (zh) * 2022-03-14 2023-09-22 中国电信股份有限公司 通信管理方法、装置和***

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107079353A (zh) * 2014-08-22 2017-08-18 诺基亚通信公司 新服务区中的低等待时间服务连接设立
WO2018089615A1 (en) * 2016-11-10 2018-05-17 Intel Corporation Radio access network (ran) node, mobile device and methods for configuration of a group-cast mode in a software defined network (sdn)
CN109548178A (zh) * 2018-12-26 2019-03-29 腾讯科技（深圳）有限公司 一种通信方法和网络设备

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030013449A1 (en) * 2001-07-11 2003-01-16 Hose David A. Monitoring boundary crossings in a wireless network
CN101616169B (zh) * 2008-06-23 2013-03-13 华为技术有限公司 选择服务提供实体的方法、***、服务选择实体、服务管理实体
CN102291820B (zh) * 2010-06-17 2015-04-01 电信科学技术研究院 一种寻呼的方法、***及装置
KR101814562B1 (ko) * 2014-03-21 2018-01-04 후아웨이 테크놀러지 컴퍼니 리미티드 서비스 할당을 위한 처리 방법 및 관련 장치
US9883385B2 (en) * 2015-09-15 2018-01-30 Qualcomm Incorporated Apparatus and method for mobility procedure involving mobility management entity relocation
WO2017073992A1 (ko) * 2015-10-30 2017-05-04 엘지전자 주식회사 세션을 제어하는 방법 및 장치
WO2017202342A1 (zh) * 2016-05-26 2017-11-30 中兴通讯股份有限公司 信息上报方法、装置及***
CN106102106B (zh) * 2016-06-20 2020-03-24 电信科学技术研究院 一种终端接入的方法、装置及网络架构
CN110611575B (zh) * 2016-10-31 2021-08-03 华为技术有限公司 位置变更上报方法、设备及***
CN109845216B (zh) * 2016-11-29 2020-08-25 华为技术有限公司 一种通信方法及装置
US10531420B2 (en) * 2017-01-05 2020-01-07 Huawei Technologies Co., Ltd. Systems and methods for application-friendly protocol data unit (PDU) session management
CN108419270B (zh) * 2017-02-10 2021-08-06 中兴通讯股份有限公司 一种业务分流实现方法及装置
US11737014B2 (en) * 2017-03-01 2023-08-22 Huawei Technologies Co., Ltd. Service processing method and device
KR102327639B1 (ko) * 2017-03-10 2021-11-17 삼성전자 주식회사 Mobile Initiated Communication Only mode 단말의 연결을 유지시키는 방법
US10952176B2 (en) * 2017-03-17 2021-03-16 Samsung Electronics Co., Ltd. AF influenced PDU session management and subscription procedures
CN109428749B (zh) * 2017-08-28 2022-04-22 华为技术有限公司 网络管理方法及相关设备
JP7150831B2 (ja) * 2017-09-28 2022-10-11 テレフオンアクチーボラゲット エルエム エリクソン（パブル） スライス可用性に基づく周波数又は無線アクセス技術（ｒａｔ）選択
US11013052B2 (en) * 2018-01-15 2021-05-18 Huawei Technologies Co., Ltd. Methods and systems for multicast-broadcast session release and modification
US10999787B2 (en) * 2018-02-17 2021-05-04 Huawei Technologies Co., Ltd. System and method for UE context and PDU session context management
US11382145B2 (en) * 2018-08-06 2022-07-05 Huawei Technologies Co., Ltd. Systems and methods to support group communications
US11224093B2 (en) * 2018-08-13 2022-01-11 Ofinno, Llc Network initiated UPF sessions transfer
US11641564B2 (en) * 2019-08-16 2023-05-02 Ofinno, Llc Flexible zone-based registration area tracking in a wireless network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107079353A (zh) * 2014-08-22 2017-08-18 诺基亚通信公司 新服务区中的低等待时间服务连接设立
WO2018089615A1 (en) * 2016-11-10 2018-05-17 Intel Corporation Radio access network (ran) node, mobile device and methods for configuration of a group-cast mode in a software defined network (sdn)
CN109548178A (zh) * 2018-12-26 2019-03-29 腾讯科技（深圳）有限公司 一种通信方法和网络设备

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
3GPP: "3GPP Technical Specification Group Services and System Aspects; Study on Enhancements to the Service-Based Architecture (Release 16)", 3GPP TR 23.742 V16.0.0, 19 December 2018 (2018-12-19), XP051591222 *
LIU CHAO ET AL : "Research on 5G Service Based Architecture (SBA)", INFORMATION AND COMMUNICATIONS TECHNOLOGY AND POLICY, no. 11, 30 November 2018 (2018-11-30), CN, pages 31 - 35, XP009521724, ISSN: 2096-5931 *
See also references of EP3905834A4 *

Also Published As

Publication number Publication date
KR102480207B1 (ko) 2022-12-21
EP3905834A4 (en) 2022-03-02
CN109548178A (zh) 2019-03-29
CN114375069A (zh) 2022-04-19
US11595797B2 (en) 2023-02-28
EP3905834A1 (en) 2021-11-03
US20210204104A1 (en) 2021-07-01
JP7162135B2 (ja) 2022-10-27
KR20210047923A (ko) 2021-04-30
JP2022507383A (ja) 2022-01-18
EP3905834B1 (en) 2024-04-03
CN109548178B (zh) 2022-02-08
CN114375069B (zh) 2024-04-12

Similar Documents

Publication Publication Date Title
WO2020134885A1 (zh) 一种通信方法和网络设备
US10503568B2 (en) Asynchronous handling of service requests
WO2020199792A1 (zh) 通信方法、装置、计算机可读介质及电子设备
WO2021213035A1 (zh) 网络辅助信息提供方法、装置、电子设备及计算机可读存储介质
JP7410166B2 (ja) サービス要求の処理方法及び関連装置
JP2018515982A (ja) 動的仮想化ネットワーク機能記述子管理のためのシステムおよび方法
US11237888B2 (en) Message processing method and system, storage medium and electronic device
CN110162314A (zh) 一种软件升级管理的方法、服务器、终端、装置及存储介质
JP2019523605A (ja) ネットワークポリシー更新のトリガー方法、管理機能エンティティおよびコアネットワークデバイス
WO2023103599A1 (zh) 投屏方法、装置、存储介质及电子设备
JP2024081633A (ja) サービス要求の処理
JP2013535736A (ja) 端末管理パッケージを提供する装置及び前記端末管理パッケージを受信する方法
WO2023011107A1 (zh) 会话策略控制方法、网元、存储介质和电子设备
WO2023116131A1 (zh) 跨生态设备管控方法、装置、存储介质及电子设备
WO2022040976A1 (en) Unified graphical user interface for devices in a wireless network
CN114302463A (zh) 网络切换方法、***、设备及存储介质
WO2024146115A1 (zh) 带宽资源分配方法、装置及相关设备
WO2024032599A1 (zh) 会话绑定方法及功能、存储介质及电子设备
WO2023216921A1 (zh) 用于算力网络的装置、方法、设备、及介质
JP7495474B2 (ja) 第１のネットワークおよび第２のネットワークを介する第１デバイスと第２デバイスとの間の通信を管理するための方法
WO2023179083A1 (zh) 路由选择策略配置方法、装置、设备及存储介质
WO2019090662A1 (zh) 网络业务实现方法、装置、计算机设备及存储介质
CN116939317A (zh) 视频交互处理方法、装置、设备、存储介质和程序产品
CN115842856A (zh) 选择网络功能实例的方法、装置、电子设备和可读介质
CN118317281A (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: 19904490

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20217008747

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2021526259

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019904490

Country of ref document: EP

Effective date: 20210726