WO2020224437A1 - 一种通信方法、装置、实体及计算机可读存储介质 - Google Patents
一种通信方法、装置、实体及计算机可读存储介质 Download PDFInfo
- Publication number
- WO2020224437A1 WO2020224437A1 PCT/CN2020/086116 CN2020086116W WO2020224437A1 WO 2020224437 A1 WO2020224437 A1 WO 2020224437A1 CN 2020086116 W CN2020086116 W CN 2020086116W WO 2020224437 A1 WO2020224437 A1 WO 2020224437A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network function
- function entity
- network
- entity
- service
- Prior art date
- Legal status (The legal status 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 status listed.)
- Ceased
Links
Images
Classifications
-
- 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/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/30—Services specially adapted for particular environments, situations or purposes
- H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
- H04L41/5012—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] determining service availability, e.g. which services are available at a certain point in time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
- H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1012—Server selection for load balancing based on compliance of requirements or conditions with available server resources
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1014—Server selection for load balancing based on the content of a request
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
- H04W52/02—Power saving arrangements
- H04W52/0209—Power saving arrangements in terminal devices
- H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
- H04W52/0248—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
-
- 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
- H04W88/182—Network node acting on behalf of an other network entity, e.g. proxy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/34—Signalling channels for network management communication
- H04L41/342—Signalling channels for network management communication between virtual entities, e.g. orchestrators, SDN or NFV entities
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
Definitions
- This application relates to the field of communication technology, and in particular to a communication method, device, entity, and computer-readable storage medium.
- the 5G communication standard formulated by the 3rd Generation Partnership Project (3rd Generation Partnership Project, 3GPP) began with Release 15, introducing network function (NF) network elements and network function services (NF Service) into the communication network.
- 3rd Generation Partnership Project 3rd Generation Partnership Project
- NF Service can be a module located on an NF network element, or a module divided in a virtualized network.
- the NF network element and NF Service in the operator's network can provide certain or certain specific services in the running state.
- the embodiment of the present application provides a communication method, which may include:
- the control function entity receives the first request sent by the N first network function entities, where the first request includes a first valid time, and the first valid time corresponds to the first network function that sent the first request
- the N is an integer, and N>0;
- the control function entity receives a second request sent by a second network function entity; the second request is used to determine a third network function entity among the N first network function entities;
- the control function entity sends a first response to the second network function entity, where the first response includes the first valid time for the third network function entity to provide the service for the second network function entity
- the third network function entity performs business communication with the third network function entity within the first valid time when the service is provided.
- the embodiment of the present application provides a communication method, which may include:
- the second network function entity sends a second request to the control function entity; the second request is used to determine the third network function entity among the N first network function entities;
- the second network function entity receives a first response sent by the control function entity, where the first response includes the first valid time for the service provided by the third network function entity, and each of the N first network function entities The first valid time of has been saved on the control function entity, the N is an integer, and N>0;
- the second network function entity performs service communication with the third network function entity within the first effective time when the service is provided by the third network function entity.
- An embodiment of the present application provides a communication device, which may include:
- the receiving module is configured to receive first requests respectively sent by N first network function entities, wherein the first request includes a first valid time, and the first valid time corresponds to the first request that sends the first request For the service provided by the network function entity, the N is an integer and N>0;
- the receiving module is configured to receive a second request sent by a second network function entity; the second request is used to determine a third network function entity among the N first network function entities;
- the sending module is configured to send a first response to the second network function entity, the first response including the first valid time for the third network function entity to provide the service for the second network function entity
- the third network function entity performs business communication with the third network function entity within the first valid time when the service is provided.
- An embodiment of the present application provides a communication device, which may include:
- a sending module configured to send a second request to the control function entity; the second request is used to determine a third network function entity among the N first network function entities;
- the receiving module is configured to receive a first response sent by the control function entity, the first response including the first valid time of the service provided by the third network function entity, and the first effective time of each of the N first network function entities A valid time has been stored on the control function entity, the N is an integer, and N>0;
- the communication module is configured to perform business communication with the third network function entity within the first effective time when the third network function entity provides the service.
- An embodiment of the present application provides a control function entity, which may include: a transceiver, a processor, and a memory; the memory is configured to store executable instructions, and when the control function entity is running, the transceiver is configured to execute the implementation of the application
- the processor executes the executable instructions stored in the memory to execute the determined steps in the communication method provided in the embodiment of the present application.
- the embodiment of the present application provides a network function entity, which may include: a transceiver, a processor, and a memory; the memory is configured to store executable instructions, and when the network function entity is running, the transceiver is used to execute the embodiment of the present application
- the processor executes the executable instructions stored in the memory to execute the determined steps in the communication method provided in the embodiments of the present application.
- the embodiment of the present application provides a computer-readable storage medium.
- the computer-readable storage medium stores executable instructions.
- the executable instructions run on a computer, the computer executes the Communication method.
- Figure 1A is a schematic diagram of a network architecture provided by an embodiment of the present application.
- FIG. 1B is a schematic diagram of a network architecture provided by an embodiment of the present application.
- Figure 2 is a schematic diagram of a communication method provided by an embodiment of the present application.
- FIG. 3 is a schematic diagram of an example of an Internet of Vehicles scenario provided by an embodiment of the present application.
- Fig. 4 is a schematic diagram of a communication method provided by an embodiment of the present application.
- Fig. 5 is a schematic diagram of a communication device provided by an embodiment of the present application.
- Fig. 6 is a schematic diagram of a communication device provided by an embodiment of the present application.
- Fig. 7 is a schematic diagram of a communication device provided by an embodiment of the present application.
- the 5G communication standard formulated by 3GPP started with Release 15, introducing NF network elements and NF Service into the communication network. Whether it is an NF network element or NF Service, it needs to be always in operation when providing services, and the operation of these NF network elements or NF Service in the network requires a large amount of electric energy.
- embodiments of the present application provide a communication method, which can control the use of each network function entity through the effective time of the service provided by the network function entity, thereby reducing the power consumption of the network function entity. Detailed descriptions are given below.
- FIG. 1A is a schematic diagram of a network architecture provided by an embodiment of the application.
- the communication system provided by the embodiment of the present application includes a first network function entity, a control function entity (in FIG. 1A, a control network element is taken as an example), and a second network function entity.
- the first network function entity and the second network function entity can be network elements or modules that perform certain or certain specific functions in the operator's network, and can be NF network elements, NF Service modules, or service communication agents (Service Communication Proxy, SCP) network element.
- NF network elements NF Service modules
- SCP Service Communication Proxy
- the first network function entity or the second network function entity may include an access and mobility management function (Access and Mobility Management Function, AMF) network element, and a session management function (Session Management Function, SMF) network element.
- AMF Access and Mobility Management Function
- SMF Session Management Function
- Element User Plane Function (UPF) network element, Policy Control Function (PCF) network element, Unified Data Management (UDM), Unified Data Repository (UDR) network element ⁇ Authorization service function (AUthentication Server Function, AUSF) network element, network slice selection function (Network Slice Selection Function, NSSF) network element, network data analysis function (Network Data Analytics Function, NWDAF) network element or network repository function (Network Repository) Function, NRF) network element.
- UPF User Plane Function
- PCF Policy Control Function
- UDM Unified Data Management
- UDR Unified Data Repository
- AUthentication Server Function AUthentication Server Function, AUSF
- NSSF Network Slice Selection Function
- the first network function entity or the second network function entity is the NF Service module, it may be the function module of the service provided by these network elements, such as: AMF Service module, SMF Service module, UPF Service module, PCF Service module, UDM Service module, UDR Service module, AUSF Service module, NSSF Service module, NWDAF Service module or NRF Service module.
- the first network function entity or the second network function entity is an SCP network element, it may be a device that acts as a proxy for the function of the aforementioned NF network element or NF Service module.
- the control function entity can be a network element with registration and storage functions, such as a Network Repository Function (NRF) network element, and the control function entity can also be a service module with registration and storage functions, such as the NRF Service module.
- NRF Network Repository Function
- first network function entities there may be one or more first network function entities, and there may also be one or more second network function entities.
- Each first network function entity will have a first valid time.
- the functional entity may send its own first effective time to the control functional entity, and the control functional entity may store the first effective time of each first network functional entity.
- the second network function entity needs to use the third network function entity, it can obtain the first valid time of the third network function entity from the control function entity, where the third network function entity is one or more of the first network function entities.
- One of the first network function entity and the second network function entity may be a producer, and the other may be a consumer.
- the AMF network element when the SMF network element is used as the first network function entity, the AMF network element may be used as the second network function entity; when the source AMF network element is used as the first network function entity, the target AMF network element may be used as the second network function entity; When the source SMF network element is used as the first network functional entity, the target SMF network element can be used as the second network functional entity; when the UPF network element is used as the first network functional entity, the SMF network element can be used as the second network functional entity; When the network element is used as the first network function entity, the AMF network element may be used as the second network function entity, and the SMF network element may also be used as the second network function entity.
- the producer-consumer relationship between the entities is not limited to the ones listed here. If the two entities can communicate with each other, the relationship between the first network function entity and the second network function entity can be established. The relationship between producers and consumers. Of course, producers and consumers can also be at the level of SCP network elements.
- an AMF network element can include one or more AMF Service modules, which can be marked It is AMF Service 1/2/3/...
- SMF network element can include one or more SMF Service modules, which can be marked as SMF Service 1/2/3/..., when SMF Service 1/2/3/...
- AMF Service 1 can be used as the second network functional entity.
- AMF Service 2 can also be used as the second network functional entity.
- the embodiment of this application only uses this method as an example. In fact, for other networks The relationship between the service modules in the element can all be inferred based on the relationship between the producer and the consumer between the aforementioned network elements.
- the above-mentioned relationship between the producer and the consumer is relative and not fixed.
- the relationship between the two can be determined according to different usage scenarios, which is not limited in the embodiment of the present application.
- the embodiment of the present application also provides a schematic diagram of the network architecture as shown in FIG. 1B.
- the terminal device 100 is connected to the second network functional entity 300 through the network 200.
- the network 200 may be a wide area network or a local area network, or a combination of the two.
- the terminal device 100 can be implemented as notebook computers, tablet computers, desktop computers, set-top boxes, mobile devices (for example, mobile phones, portable music players, personal digital assistants, dedicated messaging devices, portable game devices) and other types of Terminal device, FIG. 1B only uses the terminal device 100 as a mobile terminal device as an example.
- the control function entity 400 receives a first request respectively sent by N first network function entities 500, the first request includes a first valid time, and the first valid time corresponds to the first network function that sent the first request For the services provided by the entity 500, the case where N is 3 is used as an example here.
- the control function entity 400 stores the received first valid time of the first network function entities 500-1, 500-2, and 500-3 locally.
- the user can send a service request to the second network function entity 300 through the terminal device 100 to request the required service data.
- the type of service request is not limited here, such as a video request, a navigation request or a sensor data request, etc. .
- the second network function entity 300 After receiving the service request, the second network function entity 300 generates a second request according to the service request, and sends the second request to the control function entity 400.
- the generated second request may include the ability to provide service data (referring to service data).
- the second request may also include network slice information, data network name, location information and effective time information of the terminal device 100, and so on.
- the control function entity 400 determines a third network function entity among the first network function entities 500-1 to 500-3 according to the received second request. Taking the first network function entities 500-1 to 500-3 all complying with the entity type in the second request as an example, if the effective time information included in the second request is the time period of 19:00-20:00 (for example, the user needs Browsing the video during this time period), and the first valid time of the first network function entity 500-1 is 16:00-24:00, and the first valid time of the first network function entity 500-2 is 8:00-16 00:00, the first valid time of the first network function entity 500-3 is 0:00-8:00, and the control function entity 400 determines the first network function entity 500-1 as the third network function entity.
- the control function entity 400 sends a first response to the second network function entity 300, the first response including the first valid time for the first network function entity 500-1 to provide the service.
- the second network function entity 300 After the second network function entity 300 receives the first response, it can perform business communication with the first network function entity 500-1 within the first valid time when the first network function entity 500-1 provides the service, that is, obtain the first network function entity 500-1.
- a network function entity 500-1 provides service data, and sends the service data to the terminal device 100 via the network 200.
- the terminal device 100 can display the obtained business data in the graphical interface 110.
- the power consumption of the network function entity can be reduced.
- users usually work in commercial areas during the day, and return to their own homes at night (mostly not in commercial areas), that is, the network function entities used by users during the day are usually deployed in commercial areas.
- network function entities are used in non-commercial areas.
- the operator may partially close the network function entity in the commercial area at night on weekdays, and close the network function entity in the non-commercial area during the day on weekdays.
- operators can partially close network functional entities in commercial areas during the day and open all network functional entities in non-commercial areas.
- the communication efficiency can be improved, and the power consumption of the network functional entity and the entire communication network can be reduced.
- the communication method provided by the embodiment of the present application may include:
- Step 101 The control function entity receives the first request sent by the N first network function entities respectively, and accordingly, the N first network function entities respectively send the first request to the control function entity.
- the first request includes the first valid time for the service provided by the first network function entity that sent the first request, N is an integer, and N>0.
- each first network function entity has a first effective time for providing services by itself, and the first effective time of each of the N first network function entities may be the same or different.
- the entity types of the N first network function entities may be the same or different.
- the first valid time may be a time period during which the first network function entity provides the service, or other time information that can indicate the time range during which the first network function entity provides the service.
- the first request may be a registration request or other types of requests, as long as the first valid time of the first network function entity can be sent to the control function entity, and the type of the first request is not limited.
- control function entity After the control function entity receives the first request respectively sent by the N first network function entities, it can record the corresponding relationship between the identification information of each first network function entity and the respective first valid time.
- the recording form can be through a list Record in the form, as shown in the list in Table 1:
- Table 1 Correspondence table between the identification information of the first network function entity and the respective first valid time
- Table 1 is only an example.
- the form of expression in Table 1 is not limited to the way recorded in Table 1.
- the identification information can be expressed in the form of a character string, and the first valid time can be expressed in a specific time.
- the value of the segment is expressed in a manner, or other expression manners may also be used, which is not limited in the embodiment of the present application.
- identification information in Table 1 above may be the identification of the NF network element or the identification of the NF Service module.
- Table 1 When it is the identifier of the NF network element, for example, taking the NF network element as an SMF network element, the above Table 1 can be expressed in the form of Table 2:
- Table 2 Correspondence table between the identification information of SMF network elements and the respective first valid time
- SMF network element identification information First effective time SMF network element identification 1 Effective time 1 SMF network element identification 2 Effective time 2 SMF network element identification 3 Effective time 3 ... ... SMF network element identification N Effective time N
- Table 1 When it is the identifier of the NF Service module, for example, taking the NF Service as SMF Service as an example, the above Table 1 can be expressed in the form of Table 3:
- Table 3 Correspondence table between the identification information of the SMF Service module and the respective first valid time
- SMF Service module identification information First effective time SMF Service Module ID 1 Effective time 1 SMF Service Module ID 2 Effective time 2 SMF Service Module ID 3 Effective time 3 ... ... SMF Service Module ID N Effective time N
- Table 1 When it is the identifier of the SCP network element, the above Table 1 can be expressed in the form of Table 4:
- Table 4 Correspondence between the identification information of the SCP network element and the respective first valid time
- Step 102 The control function entity receives the second request sent by the second network function entity, and accordingly, the second network function entity sends the second request to the control function entity.
- the second request may be a query request or another type of request.
- the second request is used to obtain information of the third network function entity among the N first network function entities.
- Step 103 The control function entity sends a first response to the second network function entity, and accordingly, the second network function entity receives the first response sent by the control function entity.
- the first response includes the first valid time of the service provided by the third network function entity, and the third network function entity is included in the N first network function entities.
- Step 104 The second network function entity performs business communication with the third network function entity within the first valid time when the third network function entity provides the service.
- the first network function entity will provide the control function entity with the first effective time of the service provided by the first network function entity, and then the second network function entity will request the control function entity to be included in the Nth The first effective time of the third network functional entity in a network functional entity, and then the second network functional entity communicates with the third network functional entity within the first effective time.
- This solution of controlling the services of each network function entity through the effective time can reduce the power consumption of the network function entity.
- the second request may include the entity type of the third network function entity.
- entity type refers to the functional classification or equipment classification of the first network functional entity.
- AMF is a type
- SMF is a type
- UPF is a type
- PCF is a type
- UDM is a type
- UDR is a type
- AUSF is a type. It is a category
- NSSF is a category
- NWDAF is a category
- NRF is a category.
- the service communication between the second network function entity and the third network function entity is usually established for the service requested by the terminal, so in the second request, the second network function entity will clearly indicate the network that the control function entity needs.
- the entity type of the functional entity for example, taking the scenario of the Internet of Vehicles as an example, if the second network functional entity is AMF, the entity type included in the second request is the type information of SMF.
- the method may further include: controlling the functional entity to determine a first entity set corresponding to the entity type from the N first functional entities, and the first entity set includes the third network Functional entity.
- the second request also includes at least one of the following: network slice information, data network name, location information and effective time information of the terminal requesting the service from the second network function entity.
- the control function entity may determine the third network function entity from the first entity set according to at least one of the above-mentioned network slice information, data network name, location information of the terminal requesting services from the second network function entity, and effective time information .
- the information of the network slicing in the embodiments of the present application may be a type of network slicing.
- the fifth generation (5th Generation, 5G) network adopts the form of network slicing, thereby realizing the division of network resources with suitable characteristics for services with different requirements. The requirements of different services are different, and the types of network slicing are also different.
- 5G networks adopts the form of network slicing, thereby realizing the division of network resources with suitable characteristics for services with different requirements. The requirements of different services are different, and the types of network slicing are also different.
- the solutions provided in the embodiments of the present application are not limited to 5G networks, and are applicable to all networks that include network slicing.
- eMBB enhanced Mobile BroadBand
- URLLC ultra-high-reliability and low-latency communication
- mIoT massive Internet (massive Internet) of Things
- eMBB is mainly used for applications such as ultra-high-definition video, holographic technology, augmented reality and virtual reality, and requires high network bandwidth and speed.
- URLLC is mainly used in fields such as unmanned driving, Internet of Vehicles, automatic factories and telemedicine, requiring low latency and high reliability
- mIoT is mainly used for the deployment of massive IoT sensors in measurement, construction, agriculture, logistics, and smart cities And in the home and other fields, the requirements for delay and mobility are not high.
- Tenants can rent different types of network slices according to their own needs. Tenants are mostly companies that provide various applications.
- Network slicing is actually the division of radio access network resources, core network resources, and transmission resources.
- the corresponding radio access network resources, core network resources, and transmission resources are Users provide business support.
- the network slices involved in the embodiments of this application may also be referred to as slices for short, including but not limited to slices, slice instances or slice sub-instances, where slices can select support information through a single network slice (Single Network Slice Selection Assistance Information, S-NSSAI)
- S-NSSAI Single Network Slice Selection Assistance Information
- the ID is uniquely identified
- the slice instance can be uniquely identified by the Network Slice Information (NSI) ID
- the slice sub-instance can be uniquely identified by the Network Slice Selection Information (NSSI) ID.
- NSI Network Slice Selection Information
- the Data Network Name refers to the type of network that the terminal accesses.
- the location information of the terminal may indicate the location of the terminal, and the location information of the terminal may include the Public Land Mobile Network Identity (PLMN ID), At least one of Tracking Area Identity (TAI) and Cell Global Identity (CGI), of course, can also include other information used to indicate location, so when determining the third network functional entity, you can try to determine A third network functional entity covering the location of the terminal.
- PLMN ID Public Land Mobile Network Identity
- TAI Tracking Area Identity
- CGI Cell Global Identity
- the effective time information may be the length information required for the effective time, for example, it takes 5 minutes or 1 hour, so that when the control functional entity makes a selection, it can determine a more accurate third network functional entity.
- control function entity determines the third network function entity suitable for business communication with the second network function entity according to the above series of parameters.
- control function entity may determine multiple third network function entities, and the second network function entity does not need so many third network function entities, it can make a further selection, and the execution process may be: 2.
- the network functional entity determines the fourth network functional entity from the third network functional entity according to at least one of the effective time information, the entity's capacity information and the entity's priority information; the second network functional entity is in the fourth network functional entity Perform business communication with the fourth network function entity within the first valid time of providing the service.
- the effective time information here can be analogized based on the effective time information in the second request.
- the capacity information of the entity refers to the remaining capacity of the third network function entity. For example, if the control function entity provides multiple third network function entities, the remaining capacity of some third network function entities does not meet the current service requirements. , The third network function entity will be excluded, and the third network function entity whose remaining capacity meets the current service requirements will be selected to provide service communication. When the remaining capacity of all the third network functional entities can meet the business needs of this time, the third network functional entity with the most remaining capacity is selected to provide business communication to ensure the load balance of the entire communication system to prevent partial system Overload, improve the reliability of the system.
- the priority information of an entity refers to the priority identifier of the third network function entity.
- each third network function entity can have its own priority identifier.
- the second network function entity will be selected from multiple third network function entities. , Select the third network function entity with the highest priority to provide service communication.
- the above-mentioned control function entity determines according to the above-mentioned entity type, and at least one of a series of parameters such as the above-mentioned network slice information, data network name, location information of the terminal requesting service from the second network function entity, and effective time information.
- the process of the third network function entity can be understood in conjunction with the Internet of Vehicles scenario shown in FIG. 3.
- the Internet of Vehicles scenario shown in Figure 3 includes terminal 10, radio access network (RAN) equipment 20, AMF network element 30, NRF network element 40, SMF network element 50A, SMF network element 50B, and SMF network. Yuan 50C.
- the AMF network element 30, NRF network element 40, SMF network element 50A, SMF network element 50B, and SMF network element 50C shown in Figure 3 are all independent devices.
- Figure 3 is just for ease of illustration, AMF network element 30 , NRF network element 40, SMF network element 50A, SMF network element 50B, and SMF network element 50C may be independent devices, or may be resource blocks with corresponding functions differentiated on the cloud network.
- the embodiment of the present application does not limit the expression forms of the AMF network element 30, NRF network element 40, SMF network element 50A, SMF network element 50B, and SMF network element 50C.
- SMF network element 50A, SMF network element 50B, and SMF network element 50C may all be the first network functional entity, and SMF network element 50A, SMF network element 50B, and SMF network element 50C may respectively send their respective The first valid time is sent to the NRF network element 40 for recording.
- the terminal 10 initiates a navigation request, which is sent to the AMF network element 30 through the RAN device 20.
- the AMF network element 30 sends a second request to the NRF network element 40.
- the request may include information that the entity type is an SMF network element.
- the second request may also include at least one of the following: network slice information, data network name, location information of the terminal requesting the service from the second network function entity, or valid Time information.
- the NRF network element 40 can determine the set of the first SMF network element from among the many types of network elements recorded by itself according to the information that the entity type is the SMF network element.
- the set of the first SMF network element includes a series of SMF network elements. yuan.
- the NRF network element 40 may also determine from the set of first SMF network elements a set of second SMF network elements suitable for the Internet of Vehicles scenario according to the network slice information, and the second SMF The set of network elements also includes multiple SMF network elements.
- the NRF network element 40 may also use the data network name and the location information of the terminal requesting the service from the second network function entity, and then The set of the third SMF network element is further determined from the set of the second SMF network element.
- the third SMF network element set may also include multiple SMF network elements.
- the NRF network element 40 may further filter out SMF network elements whose coverage area is closer to the terminal 10 from the set of second SMF network elements to form the third SMF network element set. Then the NRF network element 40 provides the set of the third SMF network element to the AMF network element 30 for the AMF network element 30 to choose.
- the set of the third SMF network element includes SMF network element 50A, SMF network element 50B, and SMF network element 50C.
- the AMF network element 30 may select the SMF network element according to at least one of effective time information, entity capacity information, and entity priority information.
- the following is an example of determining the SMF network element based on the effective time information and the entity's capacity information as an example.
- the AMF network element 30 selects the SMF network element based on the effective time information. For example, the AMF network element 30 needs to provide navigation services for 2 hours. If it is already 19:00, the first valid time for the service provided by the SMF network element 50A is 6:00 -22:00, the first valid time for SMF network element 50B to provide services is 4:00-20:00, and the first valid time for SMF network element 50C to provide services is 5:00-21:00, then the SMF network can be determined Both element 50A and SMF network element 50C can be selected.
- the AMF network element 30 further selects from the SMF network element 50A and the SMF network element 50C according to the capacity information of the entity. If the capacity of the SMF network element 50A and the SMF network element 50C can satisfy the navigation service this time, the SMF network element 50A with a larger capacity can be selected to provide navigation services for the terminal.
- the set of third SMF network elements including SMF network element 50A, SMF network element 50B, and SMF network element 50C as an example.
- the set of third SMF network elements may include more SMF network elements, if there are more SMF network elements, can further select the highest priority or the SMF network elements with the top priority rankings to provide navigation services for the terminal according to the priority information.
- the AMF network element 30 establishes business communication with the SMF network element 50A, provides navigation services for the terminal 10, and returns navigation data to the terminal 10.
- SMF network element 50A SMF network element 50B, and SMF network element 50C are marked.
- SMF network elements covering various time periods will provide services. These SMFs Each network element does not have to be in service all the time, so that the power consumption of the SMF network element can be effectively saved.
- the NRF network element 40 can provide at least two SMF network elements for the AMF network element 30, and use one of the provided SMF network elements as a backup SMF network element. To ensure the high availability of SMF network elements in the business process.
- the above second request does not include valid time information, so the NRF network element 40 selects the SMF network element 50B and enters the set of the third SMF network element. If the second request includes valid time information, the NRF network element 40 will not select The SMF network element 50B enters the set of the third SMF network element.
- the aforementioned AMF network element 30 made a selection based on the effective time information, excluding the SMF network element 50B. If the AMF network element 30 did not make a selection based on the effective time information, the SMF network element 50B was selected to provide services for the terminal, and the NRF network element 40 could also Before the expiration of the first valid time of the SMF network element 50B from 4:00 to 20:00, the SMF network element 50A is provided to the AMF network element 30 in time, that is, the service communication is switched to avoid affecting the service of the terminal 10.
- Fig. 3 is an example of an Internet of Vehicles scenario, so the terminal 10 may be a wireless terminal or a navigation terminal in an auto-driving vehicle.
- a terminal also referred to as user equipment (UE)
- UE user equipment
- UE user equipment
- the terminal can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal, an augmented reality (Augmented Reality, AR) terminal, and one of the industrial control (industrial control) Wireless terminal, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, and smart home ( Wireless terminals in smart home).
- a virtual reality Virtual Reality, VR
- AR Augmented Reality
- industrial control industrial control
- the first valid time of the N first network function entities in the embodiment of the present application may be updated according to requirements.
- the following describes the update process of the first valid time of some first network function entities in the embodiment of the present application with reference to FIG. 4 .
- the communication method provided by the embodiment of the present application may include:
- Step 201 The control function entity receives the third request respectively sent by the M first network function entities, and correspondingly, the M first network function entities respectively send the third request to the control function entity.
- each third request includes the second valid time for the service provided by the first network function entity that sent the third request
- M is an integer, M>0 and M ⁇ N.
- M can be 1.
- the second valid time can be the time range information used to replace the first valid time, or it can be an offset relative to the first valid time, for example: extend forward or backward at the start time point of the first valid time The shortened offset, or the offset extended backward or shortened forward at the end time point of the first valid time. You can also modify the limited effective time to infinite effective time, or modify the infinite effective time to limited effective time.
- Step 202 The control function entity correspondingly updates the respective first valid times of the M first network function entities according to the M second valid times.
- the valid time of the corresponding first network function entity in Table 1 can be correspondingly updated according to the second valid time.
- the second valid time is time range information that can replace the first valid time
- the first valid time can be replaced with the second valid time
- the first valid time is extended or shortened according to the offset to obtain a new valid time.
- Step 203 The second network function entity receives the first time update request sent by the control function entity, and the corresponding control function entity sends the first time update request to the second network function entity.
- the first time update request includes the second valid time of the service provided by the third network function entity.
- This step 203 is a step that is executed when the second network function entity and the third network function entity are still in service communication. In addition, if the second network function entity and the third network function entity are still in service communication, they can also be executed. Step 204.
- Step 204 The second network function entity receives the second time update request sent by the third network function entity.
- the second time update request includes the second valid time of the service provided by the third network function entity.
- step 204 the second valid time of the service provided by the third network function entity can be updated more quickly.
- Step 205 The second network functional entity updates the first effective time of the service provided by the third network functional entity according to the second effective time.
- step 205 is executed.
- the solution for updating the effective time provided by the embodiments of the present application can ensure the flexibility of effective time configuration of each network function entity and the accuracy of consumer use.
- the communication method provided by the embodiment of the present application may further include: the control function entity monitors the first effective time of each of the N first network function entities; when the first effective time of the Q first network function entities is When a valid time expires, delete the relevant information of the Q first network function entities, the relevant information includes the first valid time of the Q first network function entities, Q is an integer, Q>0 and Q ⁇ N.
- the communication method provided by the embodiment of the present application may further include: after the first valid time of the third network function entity expires, deleting relevant information of the third network function entity to disconnect Open business communication with a third network functional entity, and the relevant information includes the first valid time of the third network functional entity.
- control function entity or the second network function entity directly deletes it without notifying other entities, which can save the network overhead caused by notification signaling and also realize the network function entity Time-based automatic control.
- the communication device 60 may include: a receiving module 601 configured to receive first requests respectively sent by N first network function entities, where the first request includes the first valid time, And the first valid time corresponds to the service provided by the first network function entity that sent the first request, N is an integer, and N>0; the receiving module 601 is configured to receive the second request sent by the second network function entity; the second request Used to determine the third network function entity among the N first network function entities; the sending module 602 is configured to send a first response to the second network function entity, the first response including the first valid service provided by the third network function entity The time is used for the second network function entity to perform business communication with the third network function entity within the first valid time when the third network function entity provides services.
- the first network function entity will provide the control function entity with the first effective time of the service provided by the first network function entity, and then the second network function entity will request the control function entity to be included in the Nth The first effective time of the third network functional entity in a network functional entity, and then the second network functional entity communicates with the third network functional entity within the first effective time.
- This solution of controlling the services of each network function entity through the effective time can reduce the power consumption of the network function entity.
- the first valid time of each of the N first network function entities is the same.
- the communication device further includes a processing module 603 configured to determine the first corresponding entity type from the N first functional entities when the second request includes the entity type of the third network functional entity.
- the entity set, the first entity set includes a third network function entity.
- the processing module 603 is configured to, when the second request includes at least one of network slice information, data network name, location information of the terminal requesting the service from the second network function entity, and effective time information, According to the content included in the second request, the third network function entity is determined from the first entity set.
- the receiving module 601 is configured to receive a third request respectively sent by the M first network function entities, where the third request includes the second valid time for the service provided by the first network function entity that sent the third request , M is an integer, M>0 and M ⁇ N; the processing module 603 is configured to correspondingly update the first valid time of each of the M first network function entities according to the M second valid times.
- M of the M first network function entities is 1.
- the processing module 603 is configured to monitor the first valid time of each of the N first network function entities, and delete the Q first valid times when the first valid time of the Q first network function entities expires.
- the relevant information of the network function entity includes the first valid time of Q first network function entities, Q is an integer, Q>0 and Q ⁇ N.
- the first network function entity is a network function NF network element, an NF service module or a service communication agent SCP;
- the second network function entity is a network function NF network element, an NF service module or SCP.
- the communication device 70 may include: a sending module 701 configured to send a second request to the control function entity; the second request is used to determine the third of the N first network function entities Network function entity; receiving module 702, configured to receive a first response sent by a control function entity, the first response including the first valid time of the service provided by the third network function entity, and the first valid time of each of the N first network function entities It has been saved on the control function entity, N is an integer, and N>0; the communication module 703 is configured to perform business communication with the third network function entity within the first valid time when the third network function entity provides services.
- the second network function entity will request the control function entity for the first valid time of the third network function entity included in the N first network function entities, and then the second network function entity will Communicate with the third network function entity within the first valid time.
- This solution of controlling the services of each network function entity through the effective time can reduce the power consumption of the network function entity.
- the second request includes the entity type, and the second request further includes at least one of network slice information, data network name, location information of the terminal requesting the service from the second network function entity, and effective time information.
- the communication device 70 further includes a processing module 704 configured to determine the first network function entity from the third network function entity according to at least one of effective time information, entity capacity information, and entity priority information Four network function entities; the communication module 703 is configured to perform business communication with the fourth network function entity within the first valid time when the fourth network function entity provides services.
- a processing module 704 configured to determine the first network function entity from the third network function entity according to at least one of effective time information, entity capacity information, and entity priority information Four network function entities; the communication module 703 is configured to perform business communication with the fourth network function entity within the first valid time when the fourth network function entity provides services.
- the receiving module 702 is configured to receive a first time update request sent by the control function entity, the first time update request includes the second valid time of the service provided by the third network function entity; the processing module 704 is configured to The second valid time is to update the first valid time of the service provided by the third network function entity.
- the receiving module 702 is configured to receive a second time update request sent by a third network function entity, where the second time update request includes the second valid time for the service provided by the third network function entity; processing module 704, configure To update the first valid time of the service provided by the third network function entity according to the second valid time.
- the processing module 704 is configured to delete related information of the third network function entity after the first valid time of the third network function entity expires, so as to disconnect the service communication with the third network function entity,
- the related information includes the first valid time of the third network function entity.
- the control function entity, the first network function entity, or the second network function entity includes hardware structures and/or software modules corresponding to each function.
- the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software-driven hardware depends on the specific application and design constraint conditions of the technical solution. Professionals and technicians can use different methods for each specific application to implement the described functions, but such implementation should not be considered beyond the scope of the embodiments of the present application.
- control function entity Described from the perspective of a physical device, the control function entity, the first network function entity, or the second network function entity described above can be implemented by one physical device, or can be implemented by multiple physical devices, or can be a logic within one physical device. Functional unit, this embodiment of the application does not specifically limit this.
- FIG. 7 shows a schematic diagram of the hardware structure of a communication device provided by an embodiment of the application.
- the communication device includes at least one processor 801, a memory 802, and a communication line 803.
- the communication device may further include at least one of a transceiver 804 and a communication interface 806.
- the processor 801 may be a general-purpose central processing unit (Central Processing Unit, CPU), a microprocessor, an Application-Specific Integrated Circuit (ASIC), or one or more programs for controlling the execution of the program of this application. integrated circuit.
- CPU Central Processing Unit
- ASIC Application-Specific Integrated Circuit
- the communication line 803 may include a path to transmit information between the aforementioned components.
- the transceiver 804 using any device such as a transceiver, is used to communicate with other equipment or communication networks, such as Ethernet, Radio Access Network (RAN), Wireless Local Area Networks (WLAN), etc. .
- the transceiver 804 may also be a transceiver circuit or a transceiver.
- the communication device is a first network function entity, a second network function entity or a control function entity, the transceiver may be included.
- the communication device may also include a communication interface 806.
- the memory 802 can be a read-only memory (Read-Only Memory, ROM) or other types of static storage devices that can store static information and instructions, a random access memory (Random Access Memory, RAM), or other types that can store information and instructions
- the dynamic storage device can also be Electrically Erasable Programmable Read-Only Memory (EEPROM), CD-ROM (Compact Disc Read-Only Memory, CD-ROM) or other optical disk storage, optical disk storage (Including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program codes in the form of instructions or data structures and can be used by a computer Any other media accessed, but not limited to this.
- the memory may exist independently and is connected to the processor 801 through a communication line 803.
- the memory 802 may also be integrated with the processor 801.
- the memory 802 is used to store executable instructions for executing the communication method of the embodiment of the present application, and the processor 801 controls the execution.
- the processor 801 is configured to execute executable instructions stored in the memory 802, so as to implement the communication method provided in the embodiment of the present application.
- the executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
- the processor 801 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 7.
- the communication device may include multiple processors, such as the processor 801 and the processor 805 in FIG. 7.
- processors can be a single-CPU (single-CPU) processor or a multi-core (multi-CPU) processor.
- the processor here may refer to one or more devices, circuits, and/or processing cores for processing data (for example, executable instructions).
- the embodiments of the present application can divide functional units into the control functional entity, the first network functional entity, or the second network functional entity.
- each functional unit can be divided corresponding to each function, or two or More than two functions are integrated in one functional unit.
- the above-mentioned integrated functional unit can be implemented in the form of hardware or software functional unit.
- receiving module 601, sending module 602, sending module 701, and communication module 703 can all be implemented by the transceiver 804.
- Both the processing module 603 and the processing module 704 described above may be implemented by the processor 801 or the processor 805.
- the computer program product includes one or more executable instructions.
- the computer can be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
- Executable instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
- executable instructions can be transmitted from a website, computer, server, or data center through a cable (Such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
- a cable such as coaxial cable, optical fiber, digital subscriber line (DSL)
- wireless such as infrared, wireless, microwave, etc.
- the computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server or data center integrated with one or more available media.
- the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
- SSD solid state disk
- the computer-readable storage medium may be FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories.
- Various equipment may be FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories.
- Various equipment may be FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories.
- Various equipment may be FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories.
- executable instructions may be in the form of programs, software, software modules, scripts or codes, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and their It can be deployed in any form, including being deployed as an independent program or deployed as a module, component, subroutine or other unit suitable for use in a computing environment.
- executable instructions can be deployed to be executed on one computing device, or on multiple computing devices located in one location, or on multiple computing devices that are distributed in multiple locations and interconnected by a communication network Executed on.
- the N first network function entities are screened to obtain the third network function entity, which effectively meets the service communication requirements of the second network function entity.
- the second network function entity can screen the third network function entity to obtain the fourth network function entity according to at least one of effective time information, entity capacity information and entity priority information, which further improves The communication effect of business communication.
- control function entity or the second network function entity After the valid time expires, the control function entity or the second network function entity directly deletes the relevant information of the network function entity whose valid time has expired, without notifying other entities, thereby saving the network overhead caused by notification signaling. At the same time, time-based automatic control of network function entities is also realized.
- the first network function entity provides the control function entity with the first effective time of the service provided by the first network function entity, and then the second network function entity requests the control function entity to be included in the N first network function entities
- the first valid time of the third network function entity of the third network function entity, the second network function entity conducts business communication with the third network function entity within the first valid time period, and controls the service of each network function entity by setting the valid time. It realizes the saving of signaling and reduces the power consumption of the network function entity, and can be applied to various communication networks including the network function entity.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
| 第一网络功能实体的标识信息 | 第一有效时间 |
| 实体标识1 | 有效时间1 |
| 实体标识2 | 有效时间2 |
| 实体标识3 | 有效时间3 |
| … | … |
| 实体标识N | 有效时间N |
| SMF网元的标识信息 | 第一有效时间 |
| SMF网元标识1 | 有效时间1 |
| SMF网元标识2 | 有效时间2 |
| SMF网元标识3 | 有效时间3 |
| … | … |
| SMF网元标识N | 有效时间N |
| SMF Service模块的标识信息 | 第一有效时间 |
| SMF Service模块标识1 | 有效时间1 |
| SMF Service模块标识2 | 有效时间2 |
| SMF Service模块标识3 | 有效时间3 |
| … | … |
| SMF Service模块标识N | 有效时间N |
| SCP网元的标识信息 | 第一有效时间 |
| SCP网元标识1 | 有效时间1 |
| SCP网元标识2 | 有效时间2 |
| SCP网元标识3 | 有效时间3 |
| … | … |
| SCP网元标识N | 有效时间N |
Claims (20)
- 一种通信方法,包括:控制功能实体接收N个第一网络功能实体分别发送的第一请求,其中,所述第一请求包括第一有效时间,且所述第一有效时间对应发送所述第一请求的第一网络功能实体提供的服务,所述N为整数,且N>0;所述控制功能实体接收第二网络功能实体发送的第二请求;所述第二请求用于确定所述N个第一网络功能实体中的第三网络功能实体;所述控制功能实体向所述第二网络功能实体发送第一响应,所述第一响应包括所述第三网络功能实体提供服务的第一有效时间,用于供所述第二网络功能实体在所述第三网络功能实体提供服务的第一有效时间内与所述第三网络功能实体进行业务通信。
- 根据权利要求1所述的通信方法,其中,所述N个第一网络功能实体各自的第一有效时间是相同的。
- 根据权利要求1所述的通信方法,其中,所述第二请求包括所述第三网络功能实体的实体类型,所述方法还包括:所述控制功能实体从所述N个第一网络功能实体中确定与所述实体类型对应的第一实体集合,所述第一实体集合包括所述第三网络功能实体。
- 根据权利要求3所述的通信方法,其中,所述第二请求还包括以下至少一项:网络切片的信息、数据网络名、向所述第二网络功能实体请求业务的终端的位置信息和有效时间信息,所述方法还包括:所述控制功能实体根据所述第二请求包括的内容,从所述第一实体集合中确定所述第三网络功能实体。
- 根据权利要求1-4任一项所述的通信方法,其中,所述方法还包括:所述控制功能实体接收M个第一网络功能实体分别发送的第三请求,其中,所述第三请求包括发送所述第三请求的第一网络功能实体提供服务的第二有效时间,所述M为整数,M>0且M≤N;所述控制功能实体根据M个第二有效时间,对应更新所述M个第一网络功能实体各自的第一有效时间。
- 根据权利要求5所述的通信方法,其中,所述M=1。
- 根据权利要求1-4任一项所述的通信方法,其中,所述方法还包括:所述控制功能实体监控所述N个第一网络功能实体各自的第一有效时间;当其中Q个第一网络功能实体的第一有效时间到期时,删除所述Q个第一网络功能实体的相关信息,所述相关信息包括所述Q个第一网络功能实体的第一有效时间,所述Q为整数,Q>0且所述Q≤N。
- 根据权利要求1-4任一项所述的通信方法,其中,所述第一网络功能实体为网络功能NF网元、NF服务模块或服务通信代理SCP;所述第二网络功能实体为网络功能NF网元、NF服务模块或SCP。
- 一种通信方法,包括:第二网络功能实体向控制功能实体发送第二请求;所述第二请求用于确定N个第一网络功能实体中的第三网络功能实体;所述第二网络功能实体接收所述控制功能实体发送的第一响应,所述第一响应包括所述第三网络功能实体提供服务的第一有效时间,所述N个第一网络功能实体各自的第一有效时间已保存在所述控制功能实体上,所述N为整数,且N>0;所述第二网络功能实体在所述第三网络功能实体提供服务的第一有效时间内,与所述第三网络功能实体进行业务通信。
- 根据权利要求9所述的通信方法,其中,所述第二网络功能实体接收所述控制功能实体发送的第一响应之后,所述方法还包括:所述第二网络功能实体根据有效时间信息、实体的容量信息和实体的优先级信息中的至少一项,从所述第三网络功能实体中确定第四网络功能实体;所述第二网络功能实体在所述第三网络功能实体提供服务的第一有效时间内,与所述第三网络功能实体进行业务通信,包括:所述第二网络功能实体在所述第四网络功能实体提供服务的第一有效时间内,与所述第四网络功能实体进行业务通信。
- 根据权利要求9或10所述的通信方法,其中,所述方法还包括:所述第二网络功能实体接收所述控制功能实体发送的第一时间更新请求,所述第一时间更新请求包括所述第三网络功能实体提供服务的第二有效时间;所述第二网络功能实体根据所述第二有效时间,更新所述第三网络功能实体提供服务的第一有效时间。
- 根据权利要求9或10所述的通信方法,其中,所述方法还包括:所述第二网络功能实体接收所述第三网络功能实体发送的第二时间更新请求,所述第二时间更新请求包括所述第三网络功能实体提供服务的第二有效时间;所述第二网络功能实体根据所述第二有效时间,更新所述第三网络功能实体提供服务的第一有效时间。
- 根据权利要求9或10所述的通信方法,其中,所述方法还包括:在所述第三网络功能实体的第一有效时间到期后,删除所述第三网络功能实体的相关信息,以断开与所述第三网络功能实体的业务通信,所述相关信息包括所述第三网络功能实体的第一有效时间。
- 根据权利要求9或10所述的通信方法,其中,所述第二请求包括实体类型以及以下至少一项:网络切片的信息、数据网络名、向所述第二网络功能实体请求业务的终端的位置信息和有效时间信息。
- 根据权利要求9或10所述的通信方法,其中,所述第一网络功能实体为网络功能NF网元、NF服务模块或服务通信代理SCP;所述第二网络功能实体为网络功能NF网元、NF服务模块或SCP。
- 一种通信装置,包括:接收模块,配置为接收N个第一网络功能实体分别发送的第一请求,其中,所述第一请求包括第一有效时间,且所述第一有效时间对应发送所述第一请求的第一网络功能实体提供的服务,所述N为整数,且N>0;所述接收模块,配置为接收第二网络功能实体发送的第二请求;所述第二请求用于确定所述N个第一网络功能实体中的第三网络功能实体;发送模块,配置为向所述第二网络功能实体发送第一响应,所述第一响应包括所述第三网络功能实体提供服务的第一有效时间,用于供所述第二网络功能实体在所述第三网络功能实体提供服务的第一有效时间内与所述第三网络功能实体进行业务通信。
- 一种通信装置,包括:发送模块,配置为向控制功能实体发送第二请求;所述第二请求用于确定N个第一网络功能实体中的第三网络功能实体;接收模块,配置为接收所述控制功能实体发送的第一响应,所述第一响应包括所述第三网络功能实体提供服务的第一有效时间,所述N个第一网络功能实体各自的第一有效时间已保存在所述控制功能实体上,所述N为整数,且N>0;通信模块,配置为在所述第三网络功能实体提供服务的第一有效时间内,与所述第三网络功能实体进行业务通信。
- 一种控制功能实体,包括:收发器、处理器和存储器;该存储器配置为存储可执行指令,当所述控制功能实体运行时,所述收发器配置为执行权利要求1-8任一项中的接收和发送的步骤,所述处理器执行所述存储器存储的所述可执行指令,以执行权利要求1-8任一项的通信方法中的确定的步骤。
- 一种网络功能实体,包括:收发器、处理器和存储器;所述存储器配置为存储可执行指令,当所述网络功能实体运行时,所述收发器配置为执行权利要求9-15任一项中的接收和发送的步骤,所述处理器执行所述存储器存储的所述可执行指令,以执行权利要求9-15任一项的通信方法中的确定的步骤。
- 一种计算机可读存储介质,包括可执行指令,当所述可执行指令在计算机上运行时,使得所述计算机执行如权利要求1-8任一项所述的通信方法,或者执行如权利要求9-15任一项所述的通信方法。
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| JP2021541643A JP7130142B2 (ja) | 2019-05-06 | 2020-04-22 | 通信方法、装置、エンティティ及びコンピュータ可読記憶媒体 |
| KR1020217027356A KR102513998B1 (ko) | 2019-05-06 | 2020-04-22 | 통신 방법 및 장치, 엔티티 및 컴퓨터 판독가능 저장 매체 |
| EP20802157.6A EP3968702B1 (en) | 2019-05-06 | 2020-04-22 | Determining a network function to perform service communication with another network function |
| US17/405,962 US11991036B2 (en) | 2019-05-06 | 2021-08-18 | Communication method and apparatus, entity, and computer-readable storage medium |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910372444.0 | 2019-05-06 | ||
| CN201910372444.0A CN110072273B (zh) | 2019-05-06 | 2019-05-06 | 一种通信方法、装置、实体及存储介质 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US17/405,962 Continuation US11991036B2 (en) | 2019-05-06 | 2021-08-18 | Communication method and apparatus, entity, and computer-readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2020224437A1 true WO2020224437A1 (zh) | 2020-11-12 |
Family
ID=67370238
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2020/086116 Ceased WO2020224437A1 (zh) | 2019-05-06 | 2020-04-22 | 一种通信方法、装置、实体及计算机可读存储介质 |
Country Status (6)
| Country | Link |
|---|---|
| US (1) | US11991036B2 (zh) |
| EP (1) | EP3968702B1 (zh) |
| JP (1) | JP7130142B2 (zh) |
| KR (1) | KR102513998B1 (zh) |
| CN (1) | CN110072273B (zh) |
| WO (1) | WO2020224437A1 (zh) |
Families Citing this family (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113039763B (zh) | 2018-11-14 | 2024-05-24 | 瑞典爱立信有限公司 | 使用nf之间的直接信令的nf服务消费者重启检测 |
| CN110072273B (zh) * | 2019-05-06 | 2022-02-15 | 腾讯科技(深圳)有限公司 | 一种通信方法、装置、实体及存储介质 |
| US10819636B1 (en) * | 2019-06-26 | 2020-10-27 | Oracle International Corporation | Methods, systems, and computer readable media for producer network function (NF) service instance wide egress rate limiting at service communication proxy (SCP) |
| US20220295353A1 (en) * | 2019-08-08 | 2022-09-15 | Samsung Electronics Co., Ltd. | Method and system for intent driven deployment and management of communication service in a wireless communication system |
| CN110569288A (zh) | 2019-09-11 | 2019-12-13 | 中兴通讯股份有限公司 | 一种数据分析方法、装置、设备和存储介质 |
| EP4029311A4 (en) | 2019-09-12 | 2023-10-11 | Telefonaktiebolaget LM Ericsson (publ.) | METHOD AND DEVICE FOR FLOW CONTROL |
| US12432126B2 (en) * | 2019-09-12 | 2025-09-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for service management |
| GB2588985B (en) * | 2019-10-04 | 2022-11-09 | Samsung Electronics Co Ltd | Network and method |
| CN115022176B (zh) * | 2019-11-06 | 2023-08-22 | 腾讯科技(深圳)有限公司 | Nwdaf网元的选择方法、装置、电子设备及可读存储介质 |
| WO2021160676A1 (en) * | 2020-02-10 | 2021-08-19 | Telefonaktiebolaget Lm Ericsson (Publ) | Routing communication in telecommunications network having multiple service communication proxies |
| CN115152320B (zh) * | 2020-02-17 | 2025-05-02 | 三星电子株式会社 | 无线通信系统中用于增强网络选择准确性的方法和装置 |
| WO2022032546A1 (zh) * | 2020-08-12 | 2022-02-17 | 华为技术有限公司 | 通信方法及装置 |
| CN116546519A (zh) * | 2022-01-26 | 2023-08-04 | 中国移动通信有限公司研究院 | 一种网络数据分析功能的选择方法、装置及设备 |
| WO2023149732A1 (en) * | 2022-02-03 | 2023-08-10 | Samsung Electronics Co., Ltd. | Method and system for managing temprary slice deployment in 3gpp |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030105846A1 (en) * | 2001-11-30 | 2003-06-05 | Koninklijke Philips Electronics N.V. | Enhanched UDDI with service push model |
| CN103516746A (zh) * | 2012-06-26 | 2014-01-15 | 中兴通讯股份有限公司 | 服务变化消息的推送方法、装置及系统 |
| CN109639829A (zh) * | 2019-01-15 | 2019-04-16 | 腾讯科技(深圳)有限公司 | 基于服务的通信方法、通信单元、服务支持单元和系统 |
| CN110072273A (zh) * | 2019-05-06 | 2019-07-30 | 腾讯科技(深圳)有限公司 | 一种通信方法、装置、实体及存储介质 |
Family Cites Families (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100521658C (zh) * | 2007-06-29 | 2009-07-29 | 清华大学 | 面向服务体系结构soa下优化服务时间的混合策略方法 |
| US8090395B2 (en) * | 2009-03-12 | 2012-01-03 | Qualcomm Incorporated | Scanning channels while a device is out of service |
| CN102427451B (zh) * | 2011-12-06 | 2014-10-22 | 宁波电业局 | 一种获取服务应用的方法与系统 |
| CN105519200B (zh) * | 2013-05-14 | 2019-06-11 | 华为技术有限公司 | 一种网络选择的方法和装置 |
| US10230573B2 (en) * | 2013-12-06 | 2019-03-12 | Nokia Solutions And Networks Oy | Management of network entity selection |
| DE102014213984A1 (de) * | 2014-07-17 | 2016-01-21 | Continental Automotive Gmbh | Verfahren zum Bereitstellen eines Dienstes |
| CN104135532B (zh) * | 2014-08-12 | 2017-06-23 | 湖南大学 | 基于OSGi的车载网服务共享中间件、实现方法及服务共享方法 |
| JP6455586B2 (ja) * | 2015-02-20 | 2019-01-23 | 日本電気株式会社 | 仮想ネットワークシステム、仮想ネットワーク制御方法、制御装置およびその制御方法と制御プログラム |
| CN107113190B (zh) * | 2015-04-03 | 2019-12-17 | 华为技术有限公司 | 一种网络管理系统、设备及方法 |
| KR101746202B1 (ko) * | 2015-06-09 | 2017-06-12 | 주식회사 케이티 | 네트워크 기능 가상화 방법 및 이를 위한 장치 |
| KR102314865B1 (ko) * | 2017-03-16 | 2021-10-19 | 삼성전자 주식회사 | 단말이 Temporary User ID(임시 사용자 식별자)를 이용해 5G 네트워크에 등록하는 방안 |
| US11055725B2 (en) * | 2017-03-20 | 2021-07-06 | HomeAdvisor, Inc. | System and method for temporal feasibility analyses |
| CN108632312B (zh) * | 2017-03-20 | 2020-01-17 | 中国移动通信有限公司研究院 | 网络功能信息交互方法及装置 |
| CA3084719C (en) | 2017-10-17 | 2024-01-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Service registration in a communications network |
| US10645583B2 (en) * | 2018-02-15 | 2020-05-05 | Nokia Technologies Oy | Security management for roaming service authorization in communication systems with service-based architecture |
| ES3048501T3 (en) * | 2018-05-15 | 2025-12-10 | Ericsson Telefon Ab L M | Signaling optimization in 3gpp analytics |
| US11265694B2 (en) * | 2020-01-24 | 2022-03-01 | T-Mobile Usa, Inc. | Network repository function (NRF) discovery control |
-
2019
- 2019-05-06 CN CN201910372444.0A patent/CN110072273B/zh active Active
-
2020
- 2020-04-22 WO PCT/CN2020/086116 patent/WO2020224437A1/zh not_active Ceased
- 2020-04-22 KR KR1020217027356A patent/KR102513998B1/ko active Active
- 2020-04-22 EP EP20802157.6A patent/EP3968702B1/en active Active
- 2020-04-22 JP JP2021541643A patent/JP7130142B2/ja active Active
-
2021
- 2021-08-18 US US17/405,962 patent/US11991036B2/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030105846A1 (en) * | 2001-11-30 | 2003-06-05 | Koninklijke Philips Electronics N.V. | Enhanched UDDI with service push model |
| CN103516746A (zh) * | 2012-06-26 | 2014-01-15 | 中兴通讯股份有限公司 | 服务变化消息的推送方法、装置及系统 |
| CN109639829A (zh) * | 2019-01-15 | 2019-04-16 | 腾讯科技(深圳)有限公司 | 基于服务的通信方法、通信单元、服务支持单元和系统 |
| CN110072273A (zh) * | 2019-05-06 | 2019-07-30 | 腾讯科技(深圳)有限公司 | 一种通信方法、装置、实体及存储介质 |
Non-Patent Citations (3)
| Title |
|---|
| ERICSSON: "Caching access tokens", 3GPP TSG-SA WG3 MEETING #92-AD HOC, S3-183089, 28 September 2018 (2018-09-28), XP051541143 * |
| See also references of EP3968702A4 * |
| TENCENT: "Update of the NF/NF service discovery result", 3GPP TSG-SA WG2 MEETING #132, S2-1903261, 12 April 2019 (2019-04-12), XP051703794 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110072273A (zh) | 2019-07-30 |
| CN110072273B (zh) | 2022-02-15 |
| US11991036B2 (en) | 2024-05-21 |
| EP3968702B1 (en) | 2025-07-23 |
| KR102513998B1 (ko) | 2023-03-27 |
| EP3968702A1 (en) | 2022-03-16 |
| KR20210119504A (ko) | 2021-10-05 |
| US20210377097A1 (en) | 2021-12-02 |
| JP7130142B2 (ja) | 2022-09-02 |
| JP2022519810A (ja) | 2022-03-25 |
| EP3968702A4 (en) | 2022-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020224437A1 (zh) | 一种通信方法、装置、实体及计算机可读存储介质 | |
| KR102928749B1 (ko) | 에지 컴퓨팅 배치에서 다중 엔티티 자원, 보안 및 서비스 관리 | |
| Aazam et al. | Cloud of things (CoT): Cloud-fog-IoT task offloading for sustainable Internet of Things | |
| Saranya et al. | Data replication in mobile edge computing systems to reduce latency in internet of things | |
| Sarkar et al. | Theoretical modelling of fog computing: a green computing paradigm to support IoT applications | |
| US11284259B2 (en) | Dynamic access policy provisioning in a device fog | |
| US12182021B2 (en) | Methods and apparatus to enable secure multi-coherent and pooled memory in an edge network | |
| US20230119552A1 (en) | Resource management mechanisms for stateful serverless clusters in edge computing | |
| KR20230043044A (ko) | 디지털 트윈 보조 회복성을 위한 방법 및 장치 | |
| US11070433B2 (en) | Network function NF management method and NF management device | |
| CN109936843A (zh) | 订阅更新方法、设备及系统 | |
| WO2016161677A1 (zh) | 一种业务卸载方法及系统 | |
| WO2024125490A1 (zh) | 无线算力调度方法、装置、网络功能及存储介质 | |
| US12260127B2 (en) | Technologies for storage and processing for distributed file systems | |
| WO2023246756A1 (zh) | 算力服务方法、装置、终端及核心网设备 | |
| CN110475270A (zh) | 一种终端参数配置方法及装置 | |
| WO2021128103A1 (zh) | 定位请求处理方法、设备及系统 | |
| US20250286916A1 (en) | Mec dual edge app registration on behalf of edge platform in dual edge deployments | |
| CN112383936A (zh) | 一种可接入用户数的评估方法和装置 | |
| CN113613184B (zh) | 流量套餐确定方法和装置 | |
| US20260081842A1 (en) | Proximity, locality, intent-based tensor optimized workload placement method and apparatus | |
| WO2021056482A1 (zh) | Ambr的控制方法、设备及系统 | |
| US20240126579A1 (en) | Bare metal as-is session | |
| CN112182340B (zh) | 物联网信息查询方法、订阅方法、装置及电子设备 | |
| CN118102213A (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: 20802157 Country of ref document: EP Kind code of ref document: A1 |
|
| ENP | Entry into the national phase |
Ref document number: 2021541643 Country of ref document: JP Kind code of ref document: A |
|
| ENP | Entry into the national phase |
Ref document number: 20217027356 Country of ref document: KR 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: 2020802157 Country of ref document: EP Effective date: 20211206 |
|
| WWG | Wipo information: grant in national office |
Ref document number: 2020802157 Country of ref document: EP |