Detailed Description
The technical scheme of the application will be described below with reference to the accompanying drawings.
Fig. 1 shows a schematic architecture of a D2D communication system. As shown in fig. 1, the D2D communication system includes UE1, UE2, and a radio access network (Radio Access Network, RAN) device. Among them, the communication between UE1 and UE2 may be performed through a communication link of the PC5 port, which may be referred to as PC5 port communication. The communication between UE1 and UE2 and the RAN may be performed through a communications link of the Uu port, which may be referred to as Uu port communication.
Wherein the PC5 port refers to an interface between two UEs, and the Uu port refers to an interface between a UE and the RAN. In addition, the communication link of the PC5 port may also be called a side-link or a D2D communication link, which is used for information transmission of the data plane and the control plane, and carries messages such as Direct Discovery (Direct Discovery), direct communication (Direct Communication), and the like.
Among other things, PC5 port communications may employ various air interface technologies, such as fifth generation (5th generation,5G) technology or long term evolution (Long Term Evolution, LTE) technology.
The UE may be a terminal, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal may also be, without limitation, a cellular telephone, a cordless telephone, a session initiation protocol (session initiation protocol) telephone, a wireless local loop (wireless local loop, WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, or the like.
RAN equipment, which can also be called access network equipment, is mainly responsible for the functions of radio resource management, service quality management, data compression, encryption and the like at the air interface side. The access network equipment may include various forms of base stations such as macro base stations, micro base stations, relay stations, access points, and the like. In systems employing different radio access technologies, the names of the base station-capable devices may be different, e.g. a gNB in a 5G system, an evolved base station (evoled NodeB, eNB or eNodeB) in an LTE system, a radio controller in the cloud radio access network (cloud radio access network, CRAN) scenario. In addition, the access network device may also be, without limitation, a relay station, an access point, a vehicle device, a wearable device, and an access network device in a future 5G network or an access network device in a future evolved public land mobile network (public land mobile network, PLMN).
It should be noted that the D2D communication architecture shown in fig. 1 may be based on a 5G communication system, or may be based on an LTE communication system, or a future communication system, without limitation.
Fig. 2 shows a schematic architecture of a 5G communication system. As shown in fig. 2, the communication system includes a terminal 201, a RAN device 202, a user plane function (user plane function, UPF) 203, a Data Network (DN) 204, an authentication server function (authentication server function, AUSF) 205, an AMF206, a session management function (session management function, SMF) 207, a network opening function (network exposure function, NEF) 208, a network function library function (network repository function, NRF) 209, a policy control function (policy control function, PCF) 210, a unified data management (udified DATA MANAGEMENT, UDM) 211, and NSSF212.
The terminal 201 mainly accesses the network and obtains services through a wireless air interface, and interacts with the RAN device 202 through the air interface, and interacts with the AMF206 of the core network through non-access stratum (NAS) signaling.
RAN202 is mainly responsible for air interface resource scheduling and air interface connection management of terminal 201 access network. Such as a gNB in a 5G system.
The UPF203 is mainly responsible for forwarding and receiving user data in the terminal. For example, the UPF may receive user data from a data network and transmit the user data to a terminal through an access network device, and may also receive user data from the terminal through the access network device and forward the user data to the data network. The transmission resources and scheduling functions in the UPF103 that serve the terminals are managed and controlled by the SMF 207.
AUSF205, which is mainly responsible for authentication and authorization of the user to ensure that the user is a legal user.
The AMF206 is mainly responsible for signaling processing parts, such as access control, mobility management, attach and detach, and gateway selection, and the AMF206 may also provide a storage resource of a control plane for a session in the terminal to store a session identifier, an SMF identifier associated with the session identifier, and the like, in case of providing services for the session.
SMF207 is responsible for user plane element selection, user plane element redirection, internet protocol (internet protocol, IP) address assignment, bearer setup, modification and release, and quality of service (quality of service, qoS) control.
NEF208 for outside opening responsible for mobile network capabilities.
NRF209 for dynamic registration of service capabilities and network function discovery in charge of network functions.
PCF210 provides policy rules to control layer network functions and is responsible for obtaining subscriber subscription information related to policy decisions.
UDM211 for unified data management supporting functions such as 3GPP authentication, user identity operation, permission grant, registration, and mobility management.
NSSF212 to 212 for performing a network slice selection function for a terminal.
The UDR213 is responsible for storage and provision of terminal subscription data or storage and provision of terminal policy data.
In the network architecture, nausf is a service-based interface presented by AUSF205, namf is a service-based interface presented by AMF206, nsmf is a service-based interface presented by SMF207, nnef is a service-based interface presented by NEF208, nnrf is a service-based interface presented by NRF209, npcf is a service-based interface presented by PCF210, nudm is a service-based interface presented by UDM211, nnssf is a service-based interface presented by NSSF, nudr is a service-based interface presented by UDR 213. N1 is a reference point between the UE201 and the AMF206, N2 is a reference point between the RAN device 202 and the AMF206, for sending NAS messages, etc., N3 is a reference point between the RAN202 and the UPF203, for transmitting data of a user plane, etc., N4 is a reference point between the SMF207 and the UPF203, for transmitting information such as tunnel identification information, data buffer indication information, and downlink data notification messages of an N3 connection, and N6 is a reference point between the UPF203 and the DN204, etc.
The following description of the terms involved in the present application will be presented.
Slicing refers to slicing the physical network of an operator into multiple logical networks to achieve one-network-multiple-use. Slicing may enable operators to build multiple private, virtual, isolated, on-demand, customized logical networks on top of one physical network, and thus may meet different requirements (e.g., latency, bandwidth, number of connections, etc.) of different industry customers for network capabilities.
The QoS requirements of a service are used to characterize the QoS requirements or demands of the service. The QoS requirements may include QoS requirement parameters such as packet delay budget (PACKET DELAY budgets), packet error rate (packet error rate), and maximum data burst size (maximum data burst volume), among others. For example, assuming that the value of each QoS requirement parameter in the QoS requirement of the vehicle-to-vehicle (vehicle to vehicle, V2V) service is as follows, the packet delay budget is 200ms, and the packet error rate is 2%, the V2V service requires the data packet delay to be lower than 200ms, and the packet error rate is not higher than 2%.
It should be noted that, in the following embodiments of the present application, names of messages between devices or names of parameters in a message are merely examples, and may be other names in specific implementations, which are not limited in particular by the embodiments of the present application. In addition, the terms and methods used in the description of the present application should not be construed as limiting.
Fig. 3 shows a schematic flow chart of a communication method of the present application, as follows.
301. The first terminal acquires the context information of the side uplink.
Wherein the side-link may be used for D2D communication between the first terminal and the second terminal. The side links may also be referred to as D2D communication links, and may also be referred to as PC5 communication links, without limitation. The PC5 communication link may refer to a PC5 port based communication link.
Wherein the context information of the side-link may be used to characterize the resource requirements, e.g. the slicing requirements or QoS requirements, of the D2D traffic carried or to be carried by the side-link. In particular, the context information of the side link may include one or more of slice information of the side link, qoS requirement information of the D2D service carried by the side link.
Wherein slice information for a side-link may be used to identify the slice for the side-link. The slice of the side-link may refer to a slice to which the side-link belongs, i.e., a slice to which resources (e.g., frequency domain resources, time domain resources) occupied by the side-link belong. For example, the frequency that the side link occupies belongs to a frequency that is pre-divided into V2V slices, and then the slice to which the side link belongs is the V2V slice.
In particular, the slice information for the side link may include one or more of a slice service type for the side link and a slice identification for the side link.
The slice service type may be V2V slice, unmanned aerial vehicle (unmanned AERIAL VEHICLE, UAV) to unmanned aerial vehicle (UAV to UAV, U2U) slice, slice for communication between mobile phones, or the like. The V2V slices may be used for V2V communications and the U2U slices may be used for communications between drones. It should be noted that if only one V2V slice exists within a PLMN, then the slice service type may also be used to identify the slice.
Wherein the slice identification may be used to identify the slice, e.g., the name of the slice, the number of the slice, etc. In particular, the slice identity may be slice selection assistance information (slice selection assistance information).
The D2D traffic carried by the side link may refer to D2D traffic carried on the side link, i.e., D2D traffic carried by the side link, e.g., V2V traffic, U2U traffic.
Further, the QoS requirement information of the D2D traffic carried by the side link may be a QoS requirement parameter in the QoS requirement of the D2D traffic carried by the side link, or the QoS requirement information of the D2D traffic carried by the side link may be an indication information of the QoS requirement of the D2D traffic carried by the side link, for example, PC5 5G quality of service identifier (PC 5 5G QoS identifier,PQI).
Specifically, the first terminal may determine QoS requirement information according to a D2D service type, and the D2D service type may be a V2V service or a U2U service. For example, there is a correspondence between the D2D service type and the QoS requirement information, and the correspondence may be preconfigured in the first terminal, or the correspondence may be obtained from the network side when the first terminal performs registration, without limitation.
302. The first terminal sends the context information of the side-link to the access network device.
Wherein the side-uplink context information is for the access network device to configure a side-uplink resource pool for D2D communication. Specifically, the first terminal may send the context information of the side link to the access network device through a core network device (for example, an AMF, a PCF, etc.), for example, the first terminal sends the context information of the side link to the AMF through a NAS message, then the AMF network element sends the context information of the side link to the PCF, and the PCF may send the context information of the side link to the access network device through the AMF after authorizing the first terminal (for details, see related description of subsequent PCF authorization), or may send the context information of the side link to the access network device through the AMF after knowing that the first terminal is authorized by the AMF. Obviously, the first terminal may also directly send the context information of the side uplink to the access network device through a radio resource control (radio resource control, RRC) message, without limitation.
Accordingly, the access network device receives the side-uplink context information. For example, the access network device receives the side-link context information directly from the first terminal, or the access network device receives the side-link context information from the PCF or AMF.
In addition, in step 302, the first terminal may periodically send the context information of the side uplink, or may send the context information of the side uplink in an event-triggered manner (see the relevant description of steps 302a-302b for details), without limitation.
It should be noted that, if the Uu port of the first terminal is in an idle state, the first terminal may execute the step 302 after the Uu port between the first terminal and the access network device is changed to a connected state, or if the Uu port of the first terminal is in a connected state, the first terminal may directly execute the step 302.
303. The access network device configures a side-link resource pool for D2D communication according to the side-link context information.
Wherein, the side-link resource pool for D2D communication may be simply referred to as a side-link resource pool, and may also be referred to as a side-link physical resource pool. The sidelink resource pool may refer to a set of time domain resources and/or frequency domain resources for D2D communication, i.e. the resources in the sidelink resource pool may each be used for D2D communication.
Wherein the time domain resources of the side-uplink resource pool may be a time range, which may be represented by a time period (e.g., 8:00-12:00) or a time length (e.g., 4 hours, 40 minutes, etc.). The frequency domain resources of the side-uplink resource pool may be a frequency range, e.g., 110-128MHz.
Illustratively, assuming that the side-uplink resource pool is characterized by { time range, frequency range } = {8:00-12:00,110-128MHz }, the side-uplink resource pool includes resources over a time range of 8:00-12:00 at frequencies 110-128 MHz.
It should be noted that, the resources in the side uplink resource pool may be used for D2D communication between terminals with Uu ports in idle states, and may also be used for D2D communication between terminals with Uu ports in connected states.
In particular, the side-uplink resource pool may comprise a slice-based side-uplink resource pool, a PQI-based side-uplink resource pool, or a slice and PQI-based side-uplink resource pool.
The slice-based side-uplink resource pool may be a side-uplink resource pool configured with granularity of slices, and different side-uplink resource pools may be configured for different slices. In other words, the slice information has a corresponding relation with the side uplink resource pool, and the side uplink resource pool corresponding to the slice identified by the slice information can be indexed or found through the slice information.
For example, for a V2V slice, a side-link resource pool of the V2V slice (which may be denoted as side-link resource pool X) is arranged, and for a U2U slice, a side-link resource pool of the U2U slice (which may be denoted as side-link resource pool Y) is arranged. For another example, for slice 1, a side-link resource pool (which may be referred to as side-link resource pool m) for slice 1 is configured, and for slice 2, a side-link resource pool (which may be referred to as side-link resource pool n) for slice 2 is configured
Further, assuming that the number of side links of a V2V slice (i.e., the number of side links occupying resources belonging to the V2V slice) is greater than the number of side links of a U2U slice (i.e., the number of side links occupying resources belonging to the U2U slice), the side-link resource pool X allocated to the V2V slice is greater than the number of resources (e.g., frequency range, or time length) in the side-link resource pool Y allocated to the U2U slice, i.e., the side-link resource pool of the V2V slice, is greater than the number of resources in the side-link resource pool of the U2U slice. Or assuming that the side-link of the V2V slice has good communication performance on one frequency (denoted as first frequency) and the side-link of the U2U slice has good communication performance on another frequency (denoted as second frequency), the side-link resource pool of the V2V slice may include the first frequency, and the side-link resource pool of the U2U slice may include the second frequency.
The side-uplink resource pool based on QoS requirements may refer to a side-uplink resource pool configured with QoS requirements as granularity, and different side-uplink resource pools may be configured for different QoS requirements. In other words, the QoS requirement information has a correspondence with the side uplink resource pool, and the side uplink resource pool corresponding to the QoS requirement information can be indexed or found by the QoS requirement information (e.g., PQI).
For example, assuming that the QoS requirement information is PQI, a side-link resource pool (which may be denoted as side-link resource pool a) of pqi=1 is configured for the QoS requirement of pqi=1, and a side-link resource pool (which may be denoted as side-link resource pool b) of pqi=2 is configured for the QoS requirement of pqi=2.
Further, assuming that the number of side links of pqi=1 is greater than the number of side links of pqi=2, the side-link resource pool a allocated to pqi=1 may be greater than the side-link resource pool b allocated to pqi=2, i.e., the number of resources in the side-link resource pool a of pqi=1 is greater than the number of resources in the side-link resource pool b of pqi=2. Or assuming that the priority corresponding to pqi=1 is higher than the priority corresponding to pqi=2, the side uplink resource pool a allocated to pqi=1 may be larger than the side uplink resource pool b allocated to pqi=2.
The size of the resource amount of the side link resource pool may be compared based on the frequency range and the time range of the side link resource pool, for example, the side link resource pool a includes all time domain resources with frequencies of 110-128MHz, the side link resource pool b includes all time domain resources with frequencies of 128-140MHz, the resource amount of the side link resource pool a is larger than the resource amount of the side link resource pool b (which may be simply referred to as that the side link resource pool a is larger than the side link resource pool b), or may be compared based on the frequency range or the time range of the side link resource pool only, for example, the side link resource pool a includes time domain resources of 8:00-12:00, the side link resource pool b includes time domain resources of 14:00-16:00, and the resource amount of the side link resource pool a is larger than the resource amount of the side link resource pool b without limitation.
Note that the resources in the side uplink resource pool of pqi=1 may be used to carry the D2D traffic of pqi=1.
The side-link of pqi=1 may refer to the side-link for carrying the D2D traffic of pqi=1. In addition, the side links of pqi=2, 3,4,..and the like have similar meanings as those of pqi=1, and are not described in detail.
Wherein, the D2D service of pqi=1 may refer to a D2D service of which QoS requirement is the QoS requirement indicated by pqi=1. In addition, D2D services of pqi=2, 3,4,..and the like have similar meanings as D2D services of pqi=1, and are not described in detail.
The side-uplink resource pool based on the slice and QoS requirements may refer to a side-uplink resource pool configured with granularity of slice and QoS requirements, and on different slices, different side-uplink resource pools may be configured for different QoS requirements. In other words, slice information and QoS requirement information have a correspondence to the side-uplink resource pool, and the side-uplink resource pool corresponding to the QoS requirement information on the slice identified by the slice information can be indexed or found by the slice information (e.g., slice type) and QoS requirement information (e.g., PQI).
For example, for QoS requirements of V2V slices and pqi=1, side-uplink resource pool 1 is configured, for QoS requirements of V2V slices and pqi=2, side-uplink resource pool 2 is configured, for QoS requirements of U2U slices and pqi=2, side-uplink resource pool 3 is configured, and so on. It can be seen that each of the side-uplink resource pools 1,2 and 3 can be indexed or looked up by slice information and PQI.
It should be noted that, the access network device may perform step 303 each time the context information of the side uplink is received, or may perform step 303 when a preset condition is met. For example, the access network device performs step 303 with a preset period, or performs step 303 when the received context information of the side uplink reaches a preset number, without limitation.
It can be seen that, by adopting the method provided by the embodiment, the terminal sends the context information of the side link to the access network device, and then the access network device configures the side link resource pool for D2D communication according to the context information of the side link, so that the access network device can dynamically configure the side link resource pool for D2D communication according to the resource requirement of the side link, thereby avoiding unreasonable configuration of the side link resource pool, for example, congestion occurs when the configuration of the side link resource pool is too small, or resource waste is caused when the configuration of the side link resource pool is too large, and further improving the resource utilization rate.
Optionally, in an implementation scenario of the foregoing embodiment, before step 302, the foregoing method further includes:
300a, the first terminal sends a first request message to the PCF and receives a first response message from the PCF.
In an alternative implementation, the first request message is used for requesting that the first terminal is authorized to perform D2D communication, and the first response message is used for indicating that the first terminal is authorized to perform D2D communication.
In another alternative implementation, the first request message carries information of D2D traffic carried by the side uplink. The information of the D2D service may be a service type of the D2D service, for example, a V2V service, or a U2U service. Accordingly, the first request message is used for requesting to authorize the first terminal to perform the D2D service carried by the side link, and the first response message is used for indicating to authorize the first terminal to perform the D2D service carried by the side link.
Accordingly, the PCF receives the first request message and sends a first response message to the first terminal according to the first request message.
Illustratively, the PCF may obtain subscription information for the first terminal from the UDM after receiving the first request message. When the subscription information shows that the first terminal has subscribed to the D2D communication, the PCF may authorize the D2D communication of the first terminal, or when the subscription information shows that the first terminal has subscribed to the V2V service, the PCF authorizes the first terminal to perform the V2V service.
It should be noted that, the authorization mentioned in the present application may be replaced by permission, and is not limited.
Under the implementation scenario, the PCF authorizes the D2D service or D2D communication of the first terminal, and the first terminal reports the context information of the side link to the access network device after the authorization, so that the validity of the context information of the side link received by the access network device is ensured, and the situation that the access network device is inaccurate in statistics due to invalid context information of the side link is avoided, so that the access network device can configure the side link resource pool more accurately.
Optionally, in another implementation scenario of the above embodiment, before step 302, the method further includes:
300b, the first terminal sends a second request message to the PCF and receives a second response message from the PCF;
the second request message is used for requesting the authorization of the context information of the side link, and the second response message is used for indicating the authorization of the context information of the side link.
Wherein, the authorizing the context information of the side uplink may refer to authorizing the first terminal to use resources in the side uplink resource pool corresponding to the context information. For example, assuming that the context information is slice information, the resources in the side-uplink resource pool corresponding to the context information refer to the resources in the side-uplink resource pool of the slice identified by the slice information. For another example, assuming that the context information is QoS requirement information of the D2D service carried by the side uplink and the QoS requirement information is pqi=1, the resource corresponding to the context information refers to the resource in the side uplink resource pool of pqi=1.
Accordingly, the PCF receives the second request message and sends a second response message to the first terminal according to the second request message.
In one example, the PCF receives a second request message carrying slice information of the side-link, obtains subscription information of the first terminal from the UDM, and if the subscription information indicates that the first terminal has subscribed to a slice identified by the slice information of the side-link, i.e., a slice subscribed to the side-link, the PCF sends a second response message to the first terminal.
In another example, the PCF receives a second request message, where the second request message carries QoS requirement information of the D2D service carried by the side uplink, obtains subscription information of the first terminal from the UDM, and if the QoS parameter in the subscription information includes a QoS requirement parameter corresponding to the QoS requirement information of the D2D service carried by the side uplink, the PCF sends a second response message to the first terminal.
Under the implementation scenario, the PCF authorizes the first terminal to use the resources in the side link resource pool corresponding to the context information, and the first terminal reports the context information of the side link to the access network equipment after authorization, so that the validity of the context information of the side link received by the access network equipment is ensured, and the situation that the access network equipment is inaccurate in statistics due to invalid context information of the side link is avoided, so that the access network equipment can configure the side link resource pool more accurately.
Alternatively, in another implementation scenario of the above embodiment, step 302 includes or is replaced with step 302a or 302b.
302A, when a side uplink resource pool corresponding to the side uplink context information is congested, the first terminal sends the side uplink context information to the access network device.
Wherein congestion of the side-link resource pool may refer to that the available side-link resources in the side-link resource pool are smaller than or equal to a first threshold, or that the resource preemption in the side-link resource pool is severe, e.g. the first terminal detects that the ratio of the used resources in the side-link resource pool is larger than a preset threshold by means of a detection mechanism of carrier sense Multiple access/collision avoidance (CARRIER SENSE Multiple ACCESS WITH Collision Avoidance, CSMA/CA). In particular, a used resource may refer to a resource for which there is already data transmission.
The first threshold may be a positive integer or 0. For example, when the available sidelink resources in the sidelink resource pool are equal to 0, it indicates that there are no available sidelink resources in the sidelink resource pool, and the sidelink resource pool is congested.
Wherein the available side-link resources may refer to side-link resources that are not used.
In one example, when the context information of the side link is slice information, the side link resource pool corresponding to the context information of the side link is a side link resource pool of a slice identified by the slice information. Reference may be made in particular to the description of the slice-based side-uplink resource pool described earlier. For example, a side-downlink resource pool of V2V slices.
Accordingly, the first terminal may determine that the side-link resource pool of the slice of the side-link is congested by determining whether available side-link resources in the side-link resource pool of the slice of the side-link are less than or equal to a first threshold, or the first terminal may receive congestion indication information from the access network device, where the congestion indication information may be used to indicate that the side-link resource pool of the slice of the side-link is congested, without limitation.
Wherein the available side uplink resources in the side uplink resource pool may be transmitted by the access network device to the first terminal without limitation.
In another example, when the context information of the side link is QoS requirement information of the D2D service carried by the side link, the side link resource pool corresponding to the context information of the side link is a side link resource pool corresponding to the QoS requirement information.
The side uplink resource pool corresponding to the QoS requirement information may refer to the side uplink resource pool indexed or searched by the QoS requirement information, and reference may be made to the description of the side uplink resource pool based on QoS requirement. For example, the QoS requirement information is pqi=2, and the side uplink resource pool corresponding to the QoS requirement information is side uplink resource pool b.
The first terminal may receive congestion indication information from the access network device, where the congestion indication information is used to indicate that congestion occurs in a side uplink resource pool corresponding to QoS requirement information of a D2D service carried by the side uplink, or the first terminal may determine whether congestion occurs in a side uplink resource pool corresponding to the QoS requirement information by determining whether available side uplink resources in the side uplink resource pool corresponding to the QoS requirement information are less than or equal to a first threshold.
Wherein the available side uplink resources in the side uplink resource pool may be transmitted by the access network device to the first terminal without limitation.
In another example, when the context information of the sidelink includes slice information and QoS requirement information of D2D traffic carried by the sidelink, the sidelink resource pool corresponding to the context information of the sidelink is a sidelink resource pool corresponding to the QoS requirement information on a slice identified by the slice information.
The side uplink resource pool corresponding to the QoS requirement information on the slice identified by the slice information may refer to the side uplink resource pool indexed or searched by the slice information and the QoS requirement information, and in particular, reference may be made to the description of the side uplink resource pool based on the slice and the QoS requirement. For example, assuming that the slice information is a V2V slice and the QoS requirement information is pqi=1, the side uplink resource pool corresponding to the QoS requirement information on the slice identified by the slice information is a side uplink resource pool of pqi=1 on the V2V slice, i.e. for the V2V slice and pqi=1, the side uplink resource pool 1 is configured.
302B, when the communication state of the side link meets the preset condition, the first terminal sends the context information of the side link to the access network device.
Wherein the communication status of the side link may be used to characterize the communication quality of the side link. In particular, the communication state may include parameters characterizing communication quality, such as signal interference of the side link, signal strength or quality of the side link, and QoS implementation of the side link (QoS achievement).
The QoS implementation of the side link may include a packet delay of the side link, a packet error rate (packet error rate) of the side link, and other QoS implementation.
Accordingly, the communication status of the side link meeting the preset condition may be used to characterize that the communication quality of the side link is poor, or the communication quality of the side link does not meet the requirements of normal communication (or D2D communication, or service, etc.), without limitation.
Illustratively, the communication state of the side link satisfying the preset condition may be classified into the following cases according to the difference of the communication states:
In case 1, when the communication state is the QoS implementation of the side link, the communication state of the side link satisfies the preset condition that the QoS implementation of the side link does not satisfy the QoS requirement of the D2D service carried by the side link.
The QoS implementation may be sent by the application server to the first terminal without limitation.
It should be noted that, when the QoS parameters of the side link include a plurality of parameters, that the QoS implementation of the side link does not meet the QoS requirement of the D2D service carried by the side link may mean that any parameter of the QoS implementation of the side link does not meet the QoS requirement.
In case 2, when the communication state is the signal strength of the side link, the communication state of the side link satisfies a preset condition that the signal strength of the side link is less than a preset strength threshold.
In case 3, when the communication state is the signal quality of the side link, the communication state of the side link satisfies a preset condition that the signal quality of the side link is less than a preset quality threshold.
In case 4, when the communication state is the signal interference of the side link, the communication state of the side link satisfies the preset condition that the signal interference of the side link is greater than the preset interference threshold.
It is noted that the application is not limited to the above-listed cases, but may also include various combinations between the above-listed cases, for example, a combination of cases 2 and 3, i.e., the communication state includes the signal strength and the signal quality of the side link, and the communication state of the side link satisfies the preset condition includes the signal strength of the side link being smaller than the preset strength threshold, and/or the signal quality of the side link being smaller than the preset quality threshold.
Optionally, in another implementation scenario of the foregoing embodiment, the foregoing method further includes:
when the side link is interrupted or deactivated, the first terminal sends first indication information to the access network device or PCF.
The first indication information may be used to indicate that the communication of the side link ends, or that the D2D service carried by the side link ends, or that the data transmission is stopped on the side link, without limitation.
Specifically, the occurrence of the interruption of the side uplink may refer to that the first terminal does not receive or transmit data or signaling through the side uplink for a preset time period. For example, the first terminal does not receive a PC5 signaling (PC 5-signaling) message over the side-link within 1 second.
Note that during D2D communication, keep-up of the sidelink may be performed by keep-alive functionality, which may be implemented by periodically sending PC5-S messages.
In particular, deactivating the side-link may refer to releasing the side-link, which may be understood as releasing context information of the side-link in particular. For example, the first terminal transmits a deactivation command to the two terminals, and the deactivation command is used to deactivate the side link. For another example, the first terminal receives a deactivation command from the second terminal, and the deactivation command is used to deactivate the side link.
Further, the method may further include the access network device receiving the first indication information and reconfiguring a side uplink resource pool for D2D communication according to the first indication information.
The reconfiguration may also be referred to as updating, without limitation.
In one example, assuming that the context information of the side uplink is slice information and the slice information is an identification of a V2V slice, the access network device updates the statistics of the side uplink on the V2V slice after receiving the first indication information. For example, the number of uplink on the V2V slice is 10 before the first indication information is received, and the number of uplink on the V2V slice is updated to 9 after the first indication information is received. Further, the access network device reconfigures the side uplink resource pool for D2D communication according to the updated number of side links. For example, the access network device adjusts the side uplink resource pool of each slice in combination with the number of the side uplinks of the U2U slice and the number of the side uplinks of the updated V2V slice, which may be specifically referred to the implementation manner of the subsequent step 303, and will not be described herein.
Optionally, in another implementation scenario of the foregoing embodiment, the foregoing method further includes:
When the first terminal is switched across the access network device, the first terminal sends second indication information to the access network device or PCF.
The second indication information may be used to indicate that the first terminal switches across access network devices, or that the first terminal switches to another access network device, without limitation.
Specifically, when the first terminal performs handover of the cross-access network device, the first terminal may send the second indication information to the access network device of the first terminal before the handover of the cross-access network device occurs. For example, the first terminal receives a handover command, where the handover command is used to instruct the first terminal to handover to the target access network device, and at this time, the first terminal sends second instruction information to the source access network device or PCF of the first terminal. In other words, when the first terminal receives a handover command for indicating handover to the target access network device, it indicates that handover occurs between the access network devices.
Further, the method may further include the access network device receiving the second indication information and reconfiguring a side uplink resource pool for D2D communication according to the second indication information.
The reconfiguration may also be referred to as updating, without limitation.
In one example, assuming that the context information of the side-link is slice information and the slice information is an identification of a V2V slice, the access network device updates the statistics of the side-link on the V2V slice after receiving the second indication information, and the access network device reconfigures the side-link pool for D2D communication according to the updated statistics of the side-link. Specific reference may be made to the above-mentioned related examples of the first indication information, which are not described herein.
Optionally, in another implementation scenario of the foregoing embodiment, the foregoing method further includes:
The access network device transmits information of the side uplink resource pool.
Accordingly, after receiving the information of the side-link resource pool, the terminal may establish a side-link with other terminals by using the resources in the side-link resource pool, so as to implement D2D communication between the two terminals.
In particular, the access network device may send the information of the side-link resource pool in a broadcast manner, or send the information of the side-link resource pool in a unicast manner. For example, the access network device carries information of the side-link resource pool through a system message block (system information block, SIB) and broadcasts the SIB.
The information of the side uplink resource pool may be information of frequency domain resources, for example, information for indicating 100-120MHz, information of time domain resources, for example, information for indicating time of 08:00-12:00 (i.e. 8 points to 12 points), information of frequency domain resources and information of time domain resources, which are not limited.
In addition, the information of the side-link resource pool can be used for the terminal with the Uu interface in an idle state or a connection state to establish a side-link with other terminals by utilizing the resources in the side-link resource pool so as to realize direct communication between the two terminals.
Optionally, in another implementation scenario of the above embodiment, step 303 includes 303a and 303b.
303A, the access network device determines the distribution situation of the side links for D2D communication according to the context information of the side links.
For example, a distribution of side links for D2D communication over different slices and/or over different QoS requirements is determined.
303B, the access network device configures a side uplink resource pool for D2D communication according to the distribution situation.
In one example, taking a side-link resource pool based on a slice as an example, and taking the side-link context information as a V2V slice as an example, assuming that before the access network device receives the side-link context information, the number of side-links on the V2V slice is 9, the number of side-links on the U2U slice is 3, the side-link resource pool of the V2V slice is all time-domain resources with frequencies of 100-120MHz, the side-link resource pool of the U2U slice is all time-domain resources with frequencies of 120-130MHz, and after receiving the side-link context information, the access network device determines that the number of side-links on the V2V slice is 10, the number of side-links on the U2U slice is 3, then the access network device configures the side-link resource pool of the V2V slice as all time-domain resources with frequencies of 100-122MHz, and the side-link resource pool of the U2U slice as all time-domain resources with frequencies of 122-130 MHz.
In another example, taking a side-link resource pool based on PQI as an example, assume that the side-link resource pool includes a side-link resource pool of pqi=1, a side-link resource pool of pqi=2, and a side-link resource pool of pqi=3, and the context information of the side-link is pqi=2, the number of side-links of pqi=1 is 2, the number of side-links of pqi=2 is 3, the number of side-links of pqi=3 is 3, the side-link resource pool of pqi=1 is all time-domain resources with frequencies on 110-120MHz, the side-link resource pool of pqi=2 is all time-domain resources with frequencies on 120-130MHz, and the side-link resource pool of pqi=3 is all time-domain resources with frequencies on 130-140 MHz; after receiving the context information of the side links, the access network device configures the side link resource pool of pqi=1 as all time domain resources with the frequency of 110-118MHz, the side link resource pool of pqi=2 as all time domain resources with the frequency of 118-130MHz, and the side link resource pool of pqi=3 as all time domain resources with the frequency of 130-140MHz, wherein the number of the side links of pqi=1 is 2, the number of the side links of pqi=2 is 4, and the number of the side links of pqi=3 is 3.
Fig. 4 shows a schematic flow chart of another communication method of an embodiment of the application, as follows.
401. The first terminal acquires the context information of the side uplink.
Wherein the side-link may be used for D2D communication between the first terminal and the second terminal.
402. The first terminal sends a second request message to the PCF.
The second request message carries context information of the side link, and the second request message can be used for requesting to authorize the first terminal to use resources corresponding to the context information.
403. And the PCF sends a second response message to the first terminal according to the second request message.
The second response message is used for indicating that the first terminal is authorized to use the resource corresponding to the context information.
It is noted that after step 403, the method further comprises 404a or 404b.
404A, the PCF sends the side-uplink context information to the access network device of the first terminal.
404B, after receiving the second response message, the first terminal sends the context information of the side uplink to the access network device.
405. The access network device configures a side-link resource pool for D2D communication according to the side-link context information.
Specifically, step 405 may refer to the related description of step 303, which is not repeated.
The side uplink, the context information, the D2D communication, the resources corresponding to the context information, the second request message, etc. may refer to the related description in the embodiment shown in fig. 3, and will not be described again.
By adopting the method provided by the embodiment, after the first terminal obtains the authorization of the PCF, the first terminal sends the context information of the side link to the access network equipment, so that the validity of the context information of the side link is ensured, the accuracy of configuring the side link resource pool based on the context information of the side link is further improved, the access network equipment configures the side link resource pool for D2D communication according to the context information of the side link, so that the access network equipment can dynamically configure the side link resource pool for D2D communication according to the resource requirement of the side link, and unreasonable configuration of the side link resource pool, for example, congestion caused by too small configuration of the side link resource pool, resource waste caused by too large configuration of the side link resource pool, and the like are avoided.
Optionally, in an implementation scenario of the foregoing embodiment, the foregoing method further includes:
the PCF receives first indication information, wherein the first indication information is used for indicating the communication end of the side uplink;
the PCF performs charging statistics on the first terminal according to the first indication information, and/or,
The PCF sends first indication information to access network equipment of the first terminal.
Accordingly, the access network device may reconfigure the side uplink resource pool for D2D communication according to the first indication information, and specifically, reference may be made to the related description in the embodiment shown in fig. 3, which is not repeated.
Specifically, the PCF performs charging statistics on the first terminal according to the first indication information, which may include determining, by the PCF in combination 402 with the second request message and the first indication information, a D2D communication time length of the first terminal, and charging D2D communication of the first terminal based on the time length. Further, the PCF may also charge in combination with QoS requirement information or slice information. It should be noted that different QoS requirements, different slices, and charging may be different.
Optionally, in another implementation scenario of the foregoing embodiment, the foregoing method further includes:
the PCF receives second indication information, wherein the second indication information is used for indicating the first terminal to switch the cross-over access network equipment;
The PCF sends second indication information to the access network device of the first terminal before the handoff occurs across the access network devices.
Accordingly, the access network device may reconfigure the side-uplink resource pool for D2D communication according to the second indication information. Reference may be made specifically to the related description in the embodiment shown in fig. 3, and no further description is given.
It will be appreciated that in the various embodiments above, the methods and/or steps implemented by the terminal device or network device may also be implemented by a component (e.g., a chip or circuit) that may be used in the terminal device or network device.
The scheme provided by the embodiment of the application is mainly introduced from the interaction angle among the network elements. Correspondingly, the embodiment of the application also provides a communication device which is used for realizing the various methods. The communication means may be a terminal device in the above method embodiment, for example, a transmitting terminal device or a receiving terminal device, or a device including the above terminal device, such as various types of vehicles, or a device including the above terminal device, such as a system chip, or the communication means may be a network device in the above method embodiment, or a device including the above network device, such as a system chip. It will be understood that, in order to achieve the above-mentioned functions, the communication device includes modules, units, or means (means) for implementing the above-mentioned methods, where the modules, units, or means may be implemented by hardware, software, or implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The embodiment of the application can divide the functional modules of the communication device according to the above method embodiment, for example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.
Fig. 5 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device 50 shown in fig. 5 includes one or more processors 501, a communication bus 502, and at least one communication interface (fig. 5 is merely exemplary to include communication interface 504, and one processor 501 is illustrated as an example). Optionally, the communication device 50 further comprises a memory 503.
The processor 501 may be a general purpose central processing unit (central processing unit, CPU), microprocessor, application-specific integrated circuit (application-SPECIFIC INTEGRATED circuit, for implementation), or one or more integrated circuits for controlling the execution of the programs of the present application.
The communication bus 502 may be a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, PCI) bus, or an extended industry standard architecture (extended industry standard architecture, EISA) bus, or the like. The bus may be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in fig. 5, but not only one bus or one type of bus. The communication bus 502 is used to connect the different components in the communication device 50 so that the different components can communicate.
The communication interface 504, which may be a transceiver module, is used to communicate with other devices or communication networks, such as ethernet, radio access network (radio access network, RAN), wireless local area network (wireless local area networks, WLAN), etc. For example, the transceiver module may be a device such as a transceiver, or the like. Optionally, the communication interface 504 may also be a transceiver circuit located in the processor 501, so as to implement signal input and signal output of the processor.
The memory 503 may be a device having a memory function. For example, but not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory) 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 any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and coupled to the processor via communication line 502. The memory may also be integrated with the processor.
The memory 503 is used to store computer instructions for implementing the present application, and is controlled by the processor 501 for execution. The processor 501 is configured to execute computer instructions stored in the memory 503, thereby implementing the resource allocation method provided in the embodiment of the present application.
Alternatively, in the embodiment of the present application, the processor 501 may perform the functions related to the processing in the resource allocation method provided in the embodiment of the present application, and the communication interface 504 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiment of the present application.
Alternatively, the computer instructions in the embodiments of the present application may be referred to as application program codes or instructions, which are not particularly limited in the embodiments of the present application.
In a particular implementation, as one embodiment, processor 501 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 5.
In a particular implementation, as one embodiment, the communication device 50 may include multiple processors, such as processor 501 and processor 508 in FIG. 5. Each of these processors may be a single-core (single-CPU) processor or may be a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer instructions).
In a specific implementation, as an embodiment, the communication device 50 may further include an output device 505 and an input device 506. The output device 505 communicates with the processor 501 and may display information in a variety of ways. For example, the output device 505 may be a Liquid Crystal Display (LCD) CRYSTAL DISPLAY, a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, or a projector (projector), or the like. The input device 506 is in communication with the processor 501 and may receive user input in a variety of ways. For example, the input device 506 may be a mouse, a keyboard, a touch screen device, a sensing device, or the like.
In a possible implementation, the processor 501 may cause the communication device 50 to perform the method performed by the first terminal in the above-described method embodiment by calling computer instructions stored in the memory 503. Therefore, reference may be made to the above method embodiments for the technical effects, which are not described herein.
In another possible implementation, the processor 501 may cause the communication apparatus 50 to perform the method performed by the access network device in the above-described method embodiment by invoking computer instructions stored in the memory 503. Therefore, reference may be made to the above method embodiments for the technical effects, which are not described herein.
In another possible implementation, processor 501 may cause communication device 50 to perform the method performed by the PCF in the method embodiment described above by invoking computer instructions stored in memory 503. Therefore, reference may be made to the above method embodiments for the technical effects, which are not described herein.
Fig. 6 is a schematic structural diagram of another communication device of an embodiment of the present application. The communication device 60 shown in fig. 6 includes a processing unit 601 and a transceiver unit 602.
The transceiver unit 602, which may also be referred to as a transceiver module, is configured to implement a transmitting and/or receiving function, and may be, for example, a transceiver circuit, a transceiver, or a communication interface. The processing unit 601 may also be referred to as a processing module, and may be, for example, at least one processor, without limitation.
In one possible design, the communication device 60 may be used to implement the functionality of the first terminal in the method embodiments shown in fig. 3 or 4.
A processing unit 601 is configured to obtain context information of a side link, where the side link is used for D2D communication between a first terminal and a second terminal. A transceiver unit 602, configured to send, to an access network device, the side-uplink context information, where the side-uplink context information is used for configuring, by the access network device, a side-uplink resource pool for D2D communication.
The context information of the side link may include one or more of slice information of the side link and QoS requirement information of D2D service carried by the side link.
The slice information may include one or more of a slice service type of the side link and a slice identification of the side link.
Optionally, the transceiver unit 602 is further configured to send a first request message to the policy control function PCF and receive a first response message from the PCF.
The first request message is used for requesting to authorize the first terminal to perform D2D communication, the first response message is used for indicating to authorize the first terminal to perform D2D communication, or the first request message carries information of D2D service borne by the side link, the first request message is used for requesting to authorize the first terminal to perform D2D service borne by the side link, and the first response message is used for indicating to authorize the first terminal to perform D2D service borne by the side link.
Optionally, the transceiver unit 602 is further configured to send a second request message to the PCF and receive a second response message from the PCF.
The second request message is used for requesting to authorize the first terminal to use resources corresponding to the context information, and the second response message is used for indicating to authorize the first terminal to use the resources corresponding to the context information.
Optionally, the transceiver 602 is specifically configured to send the context information of the side link to the access network device when congestion occurs in a side link resource pool corresponding to the context information of the side link, or send the context information of the side link to the access network device when a communication state of the side link meets a preset condition.
Optionally, the transceiver 602 is further configured to send, when the side uplink is interrupted or the side uplink is deactivated, first indication information to the access network device or PCF, where the first indication information is used to indicate that communication of the side uplink is ended, or send, when the first terminal is switched across the access network device, second indication information to the access network device or PCF, where the second indication information is used to indicate that the first terminal is switched across the access network device.
In another possible design, the communication means 60 may be used to implement the functionality of the access network device in the method embodiments shown in fig. 3 or 4.
A transceiving unit 602 for receiving context information of a side-link for D2D communication between the first terminal and the second terminal.
A processing unit 601, configured to configure a side uplink resource pool for D2D communication according to the context information of the side uplink.
The context information of the side link may include one or more of slice information of the side link and QoS requirement information of D2D service carried by the side link.
The side-link resource pool may include a slice-based side-link resource pool, a PQI-based side-link resource pool, or a slice-and PQI-based side-link resource pool.
Optionally, the transceiver 602 is further configured to receive indication information from the first terminal, where the indication information is used to indicate that the communication of the side uplink is ended, or the indication information is used to indicate that the first terminal performs handover across access network devices, and the processing unit 601 is further configured to reconfigure a side uplink resource pool for D2D communication according to the indication information.
Alternatively, the transceiver unit 602 is specifically configured to receive the side-link context information from the first terminal, or receive the side-link context information from the PCF.
In another possible design, communication device 60 may be used to implement the functionality of the PCF in the method embodiment of fig. 3 or 4.
A transceiver 602, configured to receive a first request message from a first terminal;
The processing unit 601 is configured to send a first response message to the first terminal according to the first request message.
Wherein the first request message is used for requesting to authorize the first terminal to perform D2D communication, and the first response message is used for indicating to authorize the first terminal to perform D2D communication, or
The first request message carries information of a D2D service, the first request message is used for requesting to authorize the first terminal to perform the D2D service, and the first response message is used for indicating to authorize the first terminal to perform the D2D service.
In yet another possible design, communication device 60 may be used to implement the functionality of the PCF in the method embodiment of fig. 3 or 4.
A transceiver 602, configured to receive a second request message from a first terminal, where the second request message carries context information of a side uplink, where the side uplink is used for D2D communication between the first terminal and a second terminal, and the second request message is used for requesting to authorize the first terminal to use resources corresponding to the context information.
The processing unit 601 is configured to send a second response message to the first terminal according to the second request message, where the second response message is used to indicate that the first terminal is authorized to use the resource corresponding to the context information.
The context information of the side link may include one or more of slice information of the side link and QoS requirement information of D2D service carried by the side link.
Optionally, the transceiver unit 602 is further configured to send the side-uplink context information to an access network device of the first terminal.
Optionally, the transceiver 602 is further configured to receive first indication information, where the first indication information is used to indicate that the communication of the side uplink is ended, and the processing unit 601 is further configured to perform charging statistics on the first terminal according to the first indication information, and/or send the first indication information to an access network device of the first terminal through the transceiver 602.
Optionally, the transceiver unit 602 is further configured to receive second indication information, where the second indication information is used to indicate that the first terminal performs handover of the cross-over access network device, and send the second indication information to the access network device of the first terminal before the handover of the cross-over access network device occurs.
In the embodiments of the present application, the processing module 601 is configured to receive or transmit the information or the message through the transceiver module 602, which is understood that after the transceiver module 602 receives a signal carrying the information or the message sent from the outside, the signal is sent to the processing module 601 for processing with or without signal processing. Alternatively, in the embodiment of the present application, the processing module 601 is configured to receive the above information or message through the transceiver module 602, and it is understood that after the transceiver module 602 receives a signal carrying the above information or message sent from the outside, the signal is sent to the processing module 601 for processing with or without signal processing. This is generally described herein, and will not be described in detail.
All relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.
In the present embodiment, the communication device 60 is presented in a form in which the respective functional modules are divided in an integrated manner. "unit" or "module" herein may refer to a particular ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuit, and/or other device that can provide the functionality described above. In a simple embodiment, one skilled in the art will appreciate that the communication device 60 may take the form of the communication device 50 shown in fig. 4.
The functions/implementation of the processing unit 601 and the transceiver unit 602 in fig. 6 may be implemented by the processor 501 in the communication device 50 shown in fig. 5 invoking computer instructions stored in the memory 503, for example. Or the function/implementation of the processing unit 601 in fig. 6 may be implemented by the processor 501 in the communication device 50 shown in fig. 5 invoking computer instructions stored in the memory 503, and the function/implementation of the transceiver unit 602 in fig. 6 may be implemented by the communication interface 504 in the communication device 50 shown in fig. 5.
An embodiment of the present application provides a computer readable storage medium having stored thereon computer instructions that, when executed, perform the actions of the first terminal, the access network device, or the PCF in the method embodiment shown in fig. 3 or 4.
Embodiments of the present application provide a computer program product comprising computer instructions that, when executed, perform the actions of the first terminal, access network device or PCF in the method embodiment shown in fig. 3 or 4 described above.
The embodiment of the application provides a communication system which comprises access network equipment and can also comprise PCF. Further, the first terminal may be further included.
Wherein the access network device may be configured to perform the method of the access network device in the embodiment of fig. 3 or 4, and the PCF may be configured to perform the method of the PCF in the embodiment of fig. 3 or 4.
The above embodiments may be implemented in whole or in part by software, hardware (e.g., circuitry), firmware, or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center by wired (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more sets of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.
It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B, and may mean that a exists alone, while a and B exist alone, and B exists alone, wherein a and B may be singular or plural. In addition, the character "/" herein generally indicates that the associated object is an "or" relationship, but may also indicate an "and/or" relationship, and may be understood by referring to the context.
In the present application, "at least one" means one or more, and "a plurality" means two or more. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (a, b, or c) of a, b, c, a-b, a-c, b-c, or a-b-c may be represented, wherein a, b, c may be single or plural.
It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.
In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. The storage medium includes a U disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.